eth/stagedsync: implement stage polygon sync forward #10124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eimdall-storage-refac
…tch/erigon into e35-astrid-store-renames
…gon into e35-astring-sync-stage-impl
taratorio
added a commit
that referenced
this pull request
Apr 29, 2024
Since we are going ahead with a `Bridge` component managing its own DB for state sync events and a `Heimdall` component managing its own DB for checkpoints, milestones and spans this refactor is now due. I also need this so I can integrate the new `polygon/sync` in a `PolygonSyncStage` as part of this PR - #10124 so I can implement a `polygonSyncStageStore` specifically for the sync stage integration.
…efactor-heimdall-tx-stores
…edgerwatch/erigon into e35-astring-sync-stage-impl
taratorio
changed the base branch from
e35
to
e35-astrid-refactor-heimdall-tx-stores
taratorio
added a commit
that referenced
this pull request
May 1, 2024
Will be using `NewRwTxStore` in #10124 Idea is simple - split the current store in 2: - `roTxStore` - `rwTxStore` These 2 stores wrap around a tx with snapshots reader. The `rwTxStore` wraps around the `roTxStore` for code re-use. This split removes chances of unexpected `tx is read only` errors when calling the store update methods. Also, opens up a possibility to introduce a `dbRwStore` and `dbRoStore` wrappers around `roTxStore` and `rwTxStore` if we decide to go down this path. The `dbRwStore` in particular can have ownership over the lifetime of a `rwTxStore` - make sure only 1 is open at a time for example by using a channel/mutex/semaphore or some other idea and call `Rollback` and/or `Commit`. We may need to look into transitioning these to `TemporalTx` at some point - for now let's just get this to work first.
taratorio
changed the title
battlmonstr
approved these changes
May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.