-
Notifications
You must be signed in to change notification settings - Fork 897
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
Bugfix potential chain head and worldstate inconsistency #4862
Bugfix potential chain head and worldstate inconsistency #4862
Conversation
… worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com>
Signed-off-by: garyschulte <garyschulte@gmail.com>
b723d20
to
856440e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
When do you expect to release this patch to stakers? As it stands, I am down. |
This PR does not purport to fix the underlying cause of #4784, but just mitigates the database damage from a failed fork-choice update if/when it occurs. For now the only recourse if you encounter the defect in 4784 is to resync besu. The next release which will have this PR included will be 23.1.0-beta on Dec 28th |
Given that this data issue pertains to a specific block (0x3bc82334b7902026f2e9ed64122ccf224899f014dc25823a8b30568e588f20cd, block 16243159) in my case, would you be able to recommend a quicker data fix that targets the specific block in the database? |
sent a private DM on discord. It is non-trivial to recover a database from this state. |
…#4862) * bugfix, ensure setNewHead does not move the chain head forward if the worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com> Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
…#4862) * bugfix, ensure setNewHead does not move the chain head forward if the worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com>
…#4862) * bugfix, ensure setNewHead does not move the chain head forward if the worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com>
…#4862) * bugfix, ensure setNewHead does not move the chain head forward if the worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com> Signed-off-by: garyschulte <garyschulte@gmail.com>
* Use safe block as pivot block suring snapsync (#4819) * Bugfix snapshot transaction segfaults after storage truncation (#4786) * Bugfix potential chain head and worldstate inconsistency (#4862) * Peering - disconnect worst peer (#4888) * Attempt to fix CPU spikes issue (#4867) * not block subscribe when the worldstate storage is open (#4912) Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com> Signed-off-by: garyschulte <garyschulte@gmail.com> Signed-off-by: Ameziane H <ameziane.hamlat@consensys.net> Signed-off-by: Karim TAAM <karim.t2am@gmail.com>
…#4862) * bugfix, ensure setNewHead does not move the chain head forward if the worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com>
…#4862) * bugfix, ensure setNewHead does not move the chain head forward if the worldstate forward fails Signed-off-by: garyschulte <garyschulte@gmail.com>
PR description
Ensure we do not leave the bonsai database in an inconsistent state where chain head and worldstate are at different block hashes
Fixed Issue(s)
relates to #4784
Documentation
doc-change-required
label to this PR ifupdates are required.
Changelog