-
Notifications
You must be signed in to change notification settings - Fork 175
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
evs exception: failed to form singleton view (leave processing) #37
Comments
@temeo your way could do the trick. here is my understanding, correct me if I'm wrong.
I devise another way without deciding leaving node will send messages or not. Maybe easier. Every time handle_install_timer is triggered
|
@dirtysalt The latter way should be avoided since generating messages on behalf of another node might produce surprising results if there are still messages from leaving node lingering in the network and it might not be backwards compatible. For the first analysis:
|
Starting 9 nodes concurrently, one of the nodes timed out waiting for prim at the moment prim was being rebootstrapped:
All the other aborted due to failure of reaching consensus:
It looks like leaving node failed to acknowledge all messages it had received due to exception and remaining nodes failed to reach consensus because of that.
To fix this, remaining nodes must decide at some point that leaving node won't be sending any more messages and ignore its safe seq in consensus computation. Raised suspected flag could be one such an indication.
The text was updated successfully, but these errors were encountered: