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.

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

Support for arbiter/temporary master node #32462

Closed
vbohata opened this issue Jul 30, 2018 · 2 comments
Closed

Support for arbiter/temporary master node #32462

vbohata opened this issue Jul 30, 2018 · 2 comments
Labels
:Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection.

Comments

@vbohata
Copy link

vbohata commented Jul 30, 2018

It would be great to be able to make one of master nodes arbiter/temporary master. We have 3 independent locations - 2 fast location and 1 slow location. It is not a good idea to have a active master node in the slow location but in case of outage of the fast location it would be great to have one in this slow location.

So I would like to be able to configure something like: make me master only if necessary and in case of 3 master-eligible nodes available give it up and let one of the master nodes in fast location drive the cluster.

Btw. in this case it will be never required to be master-node in slow location active. So something like "quorum_only" or "arbiter_only" config option would be great.

@DaveCTurner DaveCTurner added the :Distributed Coordination/Cluster Coordination Cluster formation and cluster state publication, including cluster membership and fault detection. label Jul 30, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@DaveCTurner
Copy link
Contributor

Duplicate of #14340. It's tricky, and probably depends on #32006.

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

No branches or pull requests

3 participants