Problem with master node

I'd setup the 3 node master
for node 1 the configuration was

node.name: master1
nod.data: false
node.master: true
node.voting_only: true

for node 2 the configuration was

node.name: master2
nod.data: false
node.master: true
node.voting_only: true

for node 3 the configuration was

node.name: master3
nod.data: false
node.master: true
node.voting_only: true

The problem i had faced during that time was none of the nodes was elect as master node to elect master node i made some changes in configuration file of each node (elasticsearch.yml)

for node 1

node.name: master1
nod.data: false
node.master: true
node.voting_only: true

for node 2

node.name: master2
nod.data: false
node.master: true
node.voting_only: false

for node 3

node.name: master3
nod.data: false
node.master: true
node.voting_only: false

when i did this
http://XXXX:9200/_cat/indices?v&pretty
i saw that master3 was elected as master

for testing purpose i did some changes again... i have set node.voting_only: false in each node and restart all the elasticsearch nodes
then i again hit this http://XXXX:9200/_cat/indices?v&pretty
master1 was elected as master
Now my question how to configure a node for master and do all the master nodes work parallely that is if node 1 is elected as master then what other nodes do when they are not elected as a master

Only one node will ever be elected master in a cluster at any point in time. The master eligible nodes that are not elected monitor the master node and are ready to step in if required. Voting only nodes will monitor but never step in so you should generally not have more than one in a cluster. If all nodes are equal you should not make any of them voting only.

If you are using dedicated master nodes some of them should be largely idle, but that is the price to pay for stability and high availability.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.