From c9d4d401692f59041946e484499e0b0ade669d49 Mon Sep 17 00:00:00 2001 From: Jason Tedor Date: Fri, 7 Aug 2015 11:30:36 -0400 Subject: [PATCH] Explain which nodes participate in master election This commit updates the Zen Discovery documentation to explain which nodes partcipate in master election (by default) as well as the configuration parameters for controlling this. Closes #12727 --- docs/reference/modules/discovery/zen.asciidoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/reference/modules/discovery/zen.asciidoc b/docs/reference/modules/discovery/zen.asciidoc index a0d3be9e1f9..7cca0175f3c 100644 --- a/docs/reference/modules/discovery/zen.asciidoc +++ b/docs/reference/modules/discovery/zen.asciidoc @@ -82,6 +82,12 @@ serves as a protection against (partial) network failures where node may unjustl think that the master has failed. In this case the node will simply hear from other nodes about the currently active master. +If `discovery.zen.master_election.filter_client` is `true`, pings from client nodes (nodes where `node.client` is +`true`, or both `node.data` and `node.master` are `false`) are ignored during master election; the default value is +`true`. If `discovery.zen.master_election.filter_data` is `true`, pings from non-master-eligible data nodes (nodes +where `node.data` is `true` and `node.master` is `false`) are ignored during master election; the default value is +`false`. Pings from master-eligible nodes are always observed during master election. + Nodes can be excluded from becoming a master by setting `node.master` to `false`. Note, once a node is a client node (`node.client` set to `true`), it will not be allowed to become a master (`node.master` is