feat: parity-db flush on shutdown#886
Merged
Merged
Conversation
Contributor
gilescope
approved these changes
Mar 9, 2026
gilescope
left a comment
Contributor
There was a problem hiding this comment.
I can't see it doing any harm.
ozgb
approved these changes
Mar 9, 2026
ee520c6 to
a482f88
Compare
a482f88 to
b4d3316
Compare
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
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.








Overview
This PR adds drop of parity-db once runner goes out of scope, for instance when
SIGINTorSIGTERMis generated:https://paritytech.github.io/polkadot-sdk/master/sc_cli/struct.Runner.html#method.run_node_until_exit
Before changes:
After changes:
🗹 TODO before merging
📌 Submission Checklist
🧪 Testing Evidence
Please describe any additional testing aside from CI:
🔱 Fork Strategy
Links