-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revise ledger DB disk snapshot taking policy #1264
Labels
byron
Required for a Byron mainnet: replace the old core nodes with cardano-node
chain db
consensus
issues related to ouroboros-consensus
enhancement
New feature or request
ledger db
Milestone
Comments
edsko
added
consensus
issues related to ouroboros-consensus
chain db
ledger db
priority medium
labels
Nov 20, 2019
mrBliss
added
consensus
issues related to ouroboros-consensus
priority high
and removed
consensus
issues related to ouroboros-consensus
priority medium
labels
Nov 28, 2019
I split off the most important, high priority part of this ticket to #1387. |
mrBliss
added
byron
Required for a Byron mainnet: replace the old core nodes with cardano-node
enhancement
New feature or request
priority medium
and removed
priority medium
labels
Jan 3, 2020
Even when an error occurs will a snapshot be taken on shut down. Only in case of a hard shut down while we're bulk syncing is this going to be an issue. |
edsko
changed the title
Revise ledger DB snapshot taking policy
Revise ledger DB disk snapshot taking policy
Jan 10, 2020
Note that this ticket is about on-disk snapshots; see #1026 for the in-memory snapshots. |
Re-prioritizing as high priority due to #1454 (comment) . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
byron
Required for a Byron mainnet: replace the old core nodes with cardano-node
chain db
consensus
issues related to ouroboros-consensus
enhancement
New feature or request
ledger db
We should probably
1. Take a snapshot when the node shuts downMoved to #1387.2. Adjust it so that when doing bulk sync, we take snapshots faster than once every 12 hours.
It seems that currently we also take a snapshot after replying? Not sure where/how.
The text was updated successfully, but these errors were encountered: