Hi, I have a doubt point when setup a 3 master nodes cluster. Cause the
minimum_master_nodes option's annotation in elasticsearch.yml: #Set to ensure a node sees N other master eligible nodes to be considered
operational within the cluster. Set this option to a higher value (2-4) for
large clusters (>3 nodes).
it means minimum_master_nodes not include current node self. so
Hi, I have a doubt point when setup a 3 master nodes cluster. Cause the
minimum_master_nodes option's annotation in elasticsearch.yml: #Set to ensure a node sees N other master eligible nodes to be
considered operational within the cluster. Set this option to a higher
value (2-4) for large clusters (>3 nodes).
it means minimum_master_nodes not include current node self. so
minimum_master_nodes=N/2;
but in Elasticsearch Platform — Find real-time answers at scale | Elastic #The discovery.zen.minimum_master_nodes allows to control the minimum
number of master eligible nodes a node should "see" in order to operate
within the cluster. Its recommended to set it to a higher value than 1 when
running more than 2 nodes in the cluster.
it means minimum_master_nodes should include current node self. so
On 13 December 2013 12:58, Wenbo Liang <liang...@gmail.com <javascript:>>wrote:
Hi, I have a doubt point when setup a 3 master nodes cluster. Cause the
minimum_master_nodes option's annotation in elasticsearch.yml: #Set to ensure a node sees N other master eligible nodes to be
considered operational within the cluster. Set this option to a higher
value (2-4) for large clusters (>3 nodes).
it means minimum_master_nodes not include current node self. so
minimum_master_nodes=N/2;
but in Elasticsearch Platform — Find real-time answers at scale | Elastic #The discovery.zen.minimum_master_nodes allows to control the minimum
number of master eligible nodes a node should "see" in order to operate
within the cluster. Its recommended to set it to a higher value than 1 when
running more than 2 nodes in the cluster.
it means minimum_master_nodes should include current node self. so
I have a doubt when there are two nodes which are eligible to become master. What should be the best choice for discovery.zen.minimum_master_nodes in this scenario.
According to document it is recommended to have minimum of 3 nodes.
If you have two regular nodes, you are in a conundrum. A quorum would be 2, but this means a loss of one node will make your cluster inoperable. A setting of 1 will allow your cluster to function, but doesn’t protect against split brain. It is best to have a minimum of three nodes in situations like this.
How can I prevent split brain when there are only two nodes sitting on different machine?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.