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

[Snap Sync] SNAP Phase1 and State Healing are running in the same time #4502

Closed
kamilchodola opened this issue Aug 31, 2022 · 1 comment · Fixed by #4549
Closed

[Snap Sync] SNAP Phase1 and State Healing are running in the same time #4502

kamilchodola opened this issue Aug 31, 2022 · 1 comment · Fixed by #4549
Assignees
Labels

Comments

@kamilchodola
Copy link
Contributor

Describe the bug
After few attempts of killing Nethermind process on various progress of SNAP Phase1 after following attempt, State healing and Branches started to work in parallel with Snap Phase 1 which should not be possible.

To Reproduce
Steps to reproduce the behavior (not quite accurate - hard to get exact scenario for that)

  1. Start Nethermind + Teku on Goerli and wait for OldHeaders And Downloading for new blocks to be completed
  2. When SNAP Phase 1 is started kill Teku and start it again
  3. Also in the same time try to kill Nethermind and start it again but always on Snap Phase 1 (multiple percentage)

Expected behavior
There should not be a situation when Snap Phase1 and State Healing are running in parallel

Actual behavior
After few attempts SNAP and State Healing are running in the same time which may cause db problems.
Logs attached at the end.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • Ubuntu 22
  • Nethermind from branch "blockInfo_fixes" (14.1 candidate)
  • Teku 22.8.1

Additional context
goerli.logs (1).txt

@dceleda dceleda added the sync label Aug 31, 2022
@dceleda
Copy link
Member

dceleda commented Aug 31, 2022

It shouldn't break the state, so no serious errors are expected. Although running these two state syncs in parallel is always risky and we should avoid it.
Unfortunately it can slow down the state sync.

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

Successfully merging a pull request may close this issue.

2 participants