Migrate LMDB database to RocksDB with new CLI command #2979
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
wezrule
added
enhancement
documentation
wezrule
requested review from
guilhermelawless and
SergiySW
and removed request for
guilhermelawless
wezrule
changed the title
wezrule
changed the title
|
Mainnet migration at ~55M blocks:
Second one produced a message "There was an error migrating" but everything seems fine after migrating, investigating. |
|
22GB from 21GB data.ldb. 29 minutes on i7-4970K and SATA SSD. 16GB RAM |
SergiySW
approved these changes
Oct 23, 2020
|
Worked nicely for me on V22DB11, even without being fully synced (had ~1.7M blocks), took ~5 minutes to convert. First launch afterwards was still LMDB, but then I realized I needed to update my config-node.toml. Should this be done by default for v22+? I'm assuming RocksDB will be the preferred production backend `[node.rocksdb] Whether to use the RocksDB backend for the ledger database.type:boolenable = true` |
|
Successful on 22DB11, 4 minutes. [email protected], 16GB, 1TB sata SSD. Ledger 5.8GB to 3.5GB. Ubuntu 20.04.2 |
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.
This adds a new CLI command
--migrate_database_lmdb_to_rocksdbwhich takes the LMDB database, deletes the RocksDB folder if it exists and creates an equivalent RocksDB ledger.This adds the necessary parallel for loops for the required tables, should be rebased after #2950 is in.