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

Rollback command line argument #1609

Open
eyusufatik opened this issue Dec 14, 2024 · 0 comments
Open

Rollback command line argument #1609

eyusufatik opened this issue Dec 14, 2024 · 0 comments
Milestone

Comments

@eyusufatik
Copy link
Member

eyusufatik commented Dec 14, 2024

We’ve had multiple times, on our own infra, that full nodes or the prover database got corrupted, we had to resync to the chain.

This won’t be acceptable on mainnet, what are we gonna do if the sequencer’s database gets corrupted?

Ideally, there should be two different rollback features.

  1. Invoked with a cli arg like so

    —start-L2-sync-from L2_HEIGHT —start-L1-sync from L1_HEIGHT

    This will make sure everything above certain versions for the 3 databases we have will be deleted.

  2. On startup, we check the latest versions of the 3 databases, and if we detect an anomaly, we prune the “higher” table, and start syncing form “lower” table.

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

No branches or pull requests

2 participants