Add migrator logic to evm block database #4771
Draft
Conversation
This file contains hidden or 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
DracoLi
force-pushed
the
dl/evm-blockdb-migrator
branch
from
a4c3aad to
4570360
Compare
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.
Why this should be merged
Separated the logic from #4485.
Adds migration handling for block database.
How this works
Canonical block data is migrated from the KV store to the height-indexed databases in the background.
Migrates headers, bodies, and receipts for canonical blocks; genesis is skipped.
During migration, corresponding KV entries are deleted in batches; header/body/receipt ranges are periodically compacted.
Periodic logs report status and ETA.
Migration can be paused and resumed safely.
Migrating ~71M blocks on a Mainnet node took ~5 hours.
How this was tested
Need to be documented in RELEASES.md?