Assume sharded DB in replay-verify #16058
Merged
+1
−1
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
Resolves the error where ledger metadb can't be opened under db/ledger_db, because when sharded the db should be at db/ledger_db/metadata
⏱️ 2h 31m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
|
grao1991
approved these changes
Mar 5, 2025
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.
Description
Resolves the error where ledger metadb can't be opened under db/ledger_db, because when sharded the db should be at db/ledger_db/metadata
How Has This Been Tested?
manual run
Key Areas to Review
Type of Change
Which Components or Systems Does This Change Impact?