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

Enable easy rolling back to your own local statesync snapshot #10198

Closed
4 tasks
ValarDragon opened this issue Sep 18, 2021 · 2 comments
Closed
4 tasks

Enable easy rolling back to your own local statesync snapshot #10198

ValarDragon opened this issue Sep 18, 2021 · 2 comments
Assignees

Comments

@ValarDragon
Copy link
Contributor

Summary

Currently there is no convenient method to roll back to a state snapshot that you have on your own machine. However all of the data is there (as your node will be serving it to other nodes) We should make it possible to revert your node back to a local snapshot.

As a validator, this would save me from so many issues when I accidentally do something that corrupts part of the db, and I am forced to revert my state. At the moment I have to download from a snapshot, as state sync was broken for several SDK, Tendermint version pairings, or re-state sync on pairings that work.

At upgrade time, there are a class of issues for which this is immensely helpful.

As a developer, it is very convenient to be able to quickly roll back to test something about a prior chain version, or test performance improvements against the live chain.

Proposal

Build a command that makes your own node roll back state to a prior version it has snapshotted for state sync.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@ValarDragon ValarDragon changed the title Enable easy rolling back to your own local snapshot Enable easy rolling back to your own local statesync snapshot Sep 18, 2021
@tac0turtle
Copy link
Member

This is a super needed feature also allowing someone to stop their node, snapshot, delete all other data, then restore from that snapshot would be amazing. To do both of these I believe we need the commit store exposed on the app.

@tac0turtle tac0turtle mentioned this issue Mar 7, 2022
19 tasks
@tac0turtle tac0turtle self-assigned this Mar 14, 2022
@tac0turtle tac0turtle added S:blocked Status: Blocked and removed S:blocked Status: Blocked labels May 3, 2023
@tac0turtle
Copy link
Member

completed and backported to 0.46 & 0.47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants