Skip to content

Merge master election with state recovery in the case of a full cluster restart #14016

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
Closed
bleskes opened this issue Oct 8, 2015 · 2 comments
Closed

Merge master election with state recovery in the case of a full cluster restart #14016

bleskes opened this issue Oct 8, 2015 · 2 comments
Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. >enhancement resiliency

Comments

@bleskes
Copy link
Contributor

bleskes commented Oct 8, 2015

At the moment we have a two step process - we first elect a master (based on the votes of a min_master_nodes masters). Next the elected master reaches out to at least min_master_nodes master nodes and finds the best last known cluster state. The cluster state will be used as the initial state of the cluster. We can probably merge these two into one, making sure that the elected master have the best state locally (similar to how things work in RAFT, for example). We should watch out for subtleties around honoring recover_after settings and their implications (they are mostly meant for shard recovery, so it should, in theory, be OK).
@clintongormley clintongormley added :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. and removed :Cluster labels Feb 13, 2018
@DaveCTurner DaveCTurner added the :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) label Mar 15, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@DaveCTurner DaveCTurner added :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. :Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure and removed :Distributed Indexing/Distributed A catch all label for anything in the Distributed Indexing Area. Please avoid if you can. :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) labels Mar 15, 2018
@DaveCTurner DaveCTurner added :Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. and removed :Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure labels Mar 27, 2018
@DaveCTurner
Copy link
Contributor

I think this is closed by PRs related to #32006, particularly #36013.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. >enhancement resiliency
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@clintongormley @bleskes @DaveCTurner @elasticmachine