-
Notifications
You must be signed in to change notification settings - Fork 247
Self healing open #7189
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
Merged
Merged
Self healing open #7189
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Eddy Ashton <ashton.eddy@gmail.com>
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
reviewed
Dec 18, 2025
achamayou
approved these changes
Dec 18, 2025
Co-authored-by: Amaury Chamayou <amaury@xargs.fr>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is the reification of: #7003
The idea is that if a service has fully crashed, it should be able to heal itself so long as it isn't too damaged.
Specifically, the restarting nodes should gossip the knowledge they have locally to try and elect the replica with the best local state.
The result is that after the self-healing-open one replica is chosen to recover and open, while all others restart to then join it.
The protocol can be roughly surmised as:
transition_to_openand broadcastIAmOpento the other nodes.IAmOpenfrom a trusted node, restart and join it.This still requires the submission of ledger recovery shares, however if local sealing is available those can be used instead.
UPDATE:
To be specific on when and where things happen.
createrpc it will reset the self-healing-open state and once that state is committed start several timers, one to resend gossips/votes/iamopen messages, and one to advance the failover state-machinetransition-to-openand on the next timer tick stops the timers.