-
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
max-reversible-blocks should only prevent block production #641
Comments
heifner
added a commit
that referenced
this issue
Aug 27, 2024
…, max-reversible-blocks does nothing.
heifner
added a commit
that referenced
this issue
Aug 27, 2024
heifner
added a commit
that referenced
this issue
Aug 27, 2024
heifner
added a commit
that referenced
this issue
Aug 27, 2024
…block-production [1.0] Pause production when max-reversible-blocks reached
heifner
added a commit
that referenced
this issue
Aug 27, 2024
…ersible-blocks-block-production-main
heifner
added a commit
that referenced
this issue
Aug 27, 2024
…block-production-main [1.0 -> main] Pause production when max-reversible-blocks reached
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nodeos should no longer shut down if the number of blocks in the fork database exceeds the configured
max-reversible-blocks
.Instead, when producer plugin is about to produce a block, it should check to the
block_header_state
finality_core
for the number of reversible blocks in that branch. If that exceedsmax-reversible-blocks
, then it should avoid producing the block (can just be speculating) and log a warning message.The text was updated successfully, but these errors were encountered: