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

P2P: Sync mode stuck after hitting max-reversible-blocks, after restart #565

Closed
heifner opened this issue Aug 16, 2024 · 1 comment · Fixed by #572 or #591
Closed

P2P: Sync mode stuck after hitting max-reversible-blocks, after restart #565

heifner opened this issue Aug 16, 2024 · 1 comment · Fixed by #572 or #591
Assignees
Labels
bug The product is not working as was intended. 👍 lgtm OCI Work exclusive to OCI team

Comments

@heifner
Copy link
Member

heifner commented Aug 16, 2024

After hitting max-reversible-blocks during a read-mode = irreversible sync, upon restart the node is stuck in already syncing, start sync ignored.

Hitting max-reversible-blocks should be avoided after #545. Need to investigate why node is stuck in already syncing, start sync ignored and also test #545 with the reported config.ini.

max-reversible-blocks may not work correctly with read-mode = irreversible.

@heifner heifner self-assigned this Aug 16, 2024
@heifner heifner added OCI Work exclusive to OCI team bug The product is not working as was intended. labels Aug 16, 2024
@heifner heifner moved this from Todo to In Progress in Team Backlog Aug 16, 2024
@heifner heifner added this to the Spring v1.0.0-rc2 milestone Aug 16, 2024
@heifner
Copy link
Member Author

heifner commented Aug 16, 2024

This is a different issue than #530. #530 got stuck when a block was rejected. This was stuck because it already had all the blocks requested in its forkdb, but none had been applied because the node was running in irrevsersible mode.

@arhag arhag added 👍 lgtm and removed triage labels Aug 16, 2024
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 heifner linked a pull request Aug 17, 2024 that will close this issue
@heifner heifner moved this from In Progress to Awaiting Review in Team Backlog Aug 19, 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
[1.0 -> main] Normally process blocks from the forkdb on startup
@github-project-automation github-project-automation bot moved this from Awaiting Review to Done in Team Backlog Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The product is not working as was intended. 👍 lgtm OCI Work exclusive to OCI team
Projects
Archived in project
3 participants