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

sync-check: automatically recover after a state mismatch #99

Closed
LesnyRumcajs opened this issue Jun 12, 2023 · 0 comments · Fixed by #152
Closed

sync-check: automatically recover after a state mismatch #99

LesnyRumcajs opened this issue Jun 12, 2023 · 0 comments · Fixed by #152
Assignees

Comments

@LesnyRumcajs
Copy link
Member

Issue summary

Sometimes we get state mismatches which are not really linked to the merge commit it is failing on. See ChainSafe/forest#2958

Once a state mismatch occurs, Forest won't be able to get past the offending epoch (consider it a poor man's network upgrade). The only way to get over it is to import a new snapshot. It's a workaround we need to implement in the sync check.

Pseudocode:

if run_health_check.success?
  # all good, report successful run
else
  clear_db
end

Forest should automatically grab a fresh snapshot in case the DB is gone.

Other information and links

Similar issue: #93

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

Successfully merging a pull request may close this issue.

2 participants