Skip to content
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.

Sign up for GitHub

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

Jump to bottom

raft: Use TransferLeadership to make leader demotion safer #1939

Merged
merged 1 commit into from
Feb 17, 2017
Merged

raft: Use TransferLeadership to make leader demotion safer #1939

merged 1 commit into from
Feb 17, 2017

Commits on Feb 15, 2017

  1. raft: Use TransferLeadership to make leader demotion safer 

    When we demote the leader, we currently wait for all queued messages to
be sent, as a best-effort approach to making sure the other nodes find
out that the node removal has been committed, and stop treating the
current leader as a cluster member. This doesn't work perfectly.

To make this more robust, use TransferLeadership when the leader is
trying to remove itself. The new leader's reconcilation loop will kick
in and remove the old leader.

Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
    @aaronlehmann
    aaronlehmann committed Feb 15, 2017
    Configuration menu
    Copy the full SHA
    5470e07 View commit details
    Browse the repository at this point in the history