liveBook · Manning

Master-eligible node

As explained in Elasticsearch in Action, Second Edition

A master-eligible node is an Elasticsearch node assigned the master role and therefore able to vote in master elections and become the elected master.

A master-eligible node is an Elasticsearch node assigned the master role. It is eligible to vote when the cluster elects a master and can become the elected master, but assigning the role does not make it the master immediately. A cluster has only one active master at a time. section 14.6 section 14.6.1

The active master handles cluster-wide work: allocating shards, managing indexes, and maintaining cluster state. Master-eligible nodes support this role by communicating with the master, detecting its loss, and starting an election when needed. section 14.6.1 section 14.6.2

Master-eligible nodes matter in three cluster decisions:

Minimum number of master-eligible nodes = (number of master-eligible nodes / 2) + 1

A quorum is a majority of master-eligible nodes. The cluster forms it automatically; for eight eligible nodes, the displayed rule yields five nodes. section 14.6.4

Configure a dedicated master-eligible node

For a busy cluster, isolate cluster-management work on dedicated master-eligible nodes. Set the node role to master so the node is not overloaded with data or ingest work; use at least three dedicated master-eligible nodes as a rule of thumb. section 14.6.6 section 14.7

node.roles: [ master ]

This configuration assigns the master role, making the node eligible to participate in master elections and serve as a dedicated master. section 14.6.6

Keep master-eligible nodes available and responsive. If the master is considered unavailable, eligible nodes elect a replacement; a failed cluster-state publication can also trigger a new election. Dedicated masters help prevent cluster operations from slowing or stalling under heavy indexing or search load. section 14.6.3 section 15.3.1 section 14.6.6

How Elasticsearch in Action, Second Edition covers it

How deep it goes
Explains role assignment, elections, quorum acknowledgments, split-brain risk, and dedicated-node configuration without deeper administrative coverage.
Examples
Uses an eight-eligible-node quorum calculation, a two-node split-brain scenario, and node.roles master configuration.
What it assumes
Introduces master eligibility through Elasticsearch node roles and assumes no prior cluster-election knowledge.
What you can do after
Operate/configure dedicated master-eligible nodes and evaluate quorum sizing to reduce election and split-brain risks.
How it connects
Connects master eligibility to master elections, cluster state, quorum, split brain, shard allocation, and node roles.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Elasticsearch in Action, Second Edition. The section links point to the parts of the book it draws on.