-
Notifications
You must be signed in to change notification settings - Fork 143
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
Leader does not step down? #597
Comments
👋 Thanks for opening this issue! Get help or engage by:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What about allowing the leader to continue acting as a leader after a membership config without the leader being committed?
https://github.com/drmingdrmer/consensus-bugs/#raft-suboptimal-leader-step-down
But the leader does NOT have to give up leadership:
Despite it should not cast a ballot(vote) for other candidates, a learner(AKA
non-voter, a node removed from cluster config) can nevertheless be a leader(or
become a candidate) as long as it wants. This non-voting leader:
NOTE: A learner(non-voter) does not have to reject vote requests.
Because raft ensures that a candidate using the second-to-last committed config
would never become the leader. Thanks to Gao Xinge.
Improvement
When a leader commits
, it does NOT give up leadership, but just
keep serving as leader.
This way, membership config log does not need to be dealt with specially by an
implementation. The (non-voting) leader will be removed only if it is required:
by just shutting down the non-voting leader or informing it to transfer its
leadership to another node.
The text was updated successfully, but these errors were encountered: