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
Clarify no master block #9739
Labels
Comments
I believe this is to control replication consistency in case of there is no master in your cluster. Looks like you can configure it in order to still allow reading operation (but with a probability to have stale data) or not (same for write operation). |
javanna
added a commit
that referenced
this issue
Mar 20, 2015
javanna
added a commit
that referenced
this issue
Mar 20, 2015
javanna
added a commit
that referenced
this issue
Mar 20, 2015
Thanks @ppf2 I have pushed the change that you suggested. Feel free to send a PR next time instead ;) |
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#no-master-block
"For a node to be fully operational, it must have an active master."
It may help to clarify the above with something like the following?
"For the cluster to be fully operational, it must have an active master and the number of running master eligible nodes must satisfy the discovery.zen.minimum_master_nodes setting if set."
The text was updated successfully, but these errors were encountered: