Browse Source

Remove reference to obsolete node.master (#95814)

cai-elastic 2 years ago
parent
commit
5cd135af0b
1 changed files with 6 additions and 6 deletions
  1. 6 6
      docs/reference/high-availability/cluster-design.asciidoc

+ 6 - 6
docs/reference/high-availability/cluster-design.asciidoc

@@ -86,13 +86,13 @@ template>>. <<dynamic-index-settings,Auto-expand replicas>> can also achieve
 the same thing, but it's not necessary to use this feature in such a small
 cluster.
 
-We recommend you set `node.master: false` on one of your two nodes so that it is
-not <<master-node,master-eligible>>. This means you can be certain which of your
+We recommend you set only one of your two nodes to be
+<<master-node,master-eligible>>. This means you can be certain which of your
 nodes is the elected master of the cluster. The cluster can tolerate the loss of
-the other master-ineligible node. If you don't set `node.master: false` on one
-node, both nodes are master-eligible. This means both nodes are required for a
-master election. Since the election will fail if either node is unavailable,
-your cluster cannot reliably tolerate the loss of either node.
+the other master-ineligible node. If you set both nodes to master-eligible, two
+nodes are required for a master election. Since the election will fail if either
+node is unavailable, your cluster cannot reliably tolerate the loss of either
+node.
 
 By default, each node is assigned every role. We recommend you assign both nodes
 all other roles except master eligibility. If one node fails, the other node can