Skip to content
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

Storage node sync should use checkpoints #2479

Closed
kostko opened this issue Dec 17, 2019 · 0 comments · Fixed by #3181
Closed

Storage node sync should use checkpoints #2479

kostko opened this issue Dec 17, 2019 · 0 comments · Fixed by #3181
Assignees
Labels
c:storage Category: storage

Comments

@kostko
Copy link
Member

kostko commented Dec 17, 2019

After #1920 which adds a runtime-specific pruning policy which supports querying which checkpoints should be available, the storage node sync should use checkpoints when it needs to sync too far back.

Storage checkpointing also needs to be fixed to use explicit chunks where each chunk is independently verifiable to be part of the given root. Changing this a bit will also enable us to easily use our MKVS with Tendermint's state sync (assuming we also do #1898). (This was done in #2659.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:storage Category: storage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants