-
Notifications
You must be signed in to change notification settings - Fork 10
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
P2P: Sync mode stuck after hitting max-reversible-blocks, after restart #565
Milestone
Comments
heifner
added a commit
that referenced
this issue
Aug 17, 2024
…a node that was terminated with many blocks in the forkdb
heifner
added a commit
that referenced
this issue
Aug 17, 2024
… attempt to request the next range of block instead of ignoring the request.
heifner
added a commit
that referenced
this issue
Aug 17, 2024
…s from the fork database. This allows a block stuck in a condition where it has too many blocks in the forkdb to process new blocks to attempt to apply those blocks on startup.
heifner
added a commit
that referenced
this issue
Aug 17, 2024
heifner
added a commit
that referenced
this issue
Aug 18, 2024
heifner
added a commit
that referenced
this issue
Aug 19, 2024
[1.0] Normally process blocks from the forkdb on startup
heifner
added a commit
that referenced
this issue
Aug 19, 2024
heifner
added a commit
that referenced
this issue
Aug 19, 2024
[1.0 -> main] Normally process blocks from the forkdb on startup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After hitting
max-reversible-blocks
during aread-mode = irreversible
sync, upon restart the node is stuck inalready syncing, start sync ignored
.Hitting
max-reversible-blocks
should be avoided after #545. Need to investigate why node is stuck inalready syncing, start sync ignored
and also test #545 with the reportedconfig.ini
.max-reversible-blocks
may not work correctly withread-mode = irreversible
.The text was updated successfully, but these errors were encountered: