Master not discovered
No master node could be discovered when a node attempted to join or form the cluster. Without an elected master, cluster coordination cannot proceed and nodes might fail to start.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Critical |
| Scope | Cluster |
| Domains | cluster-health, high-availability |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
No master-eligible node could be discovered to elect a cluster master.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Check network configuration
Condition: Always shown for this insight.
Verify network connectivity and firewall rules between nodes, and confirm discovery and transport settings let master-eligible nodes reach each other.
Check master node is running
Condition: Always shown for this insight.
Confirm master-eligible nodes are running, healthy, and able to participate in master election.
Check cluster bootstrapping
Condition: Always shown for this insight.
Review cluster bootstrapping and initial master discovery settings so a new or recovering cluster can elect a master on first start.
Check data node configuration
Condition: Always shown for this insight.
Verify data node roles, discovery settings, and cluster join configuration match your intended topology.
More dedicated master nodes
Condition: Always shown for this insight.
With es-data-01 master nodes and es-data-01 data nodes, add masters until the cluster has three dedicated master nodes for high availability.
When a node joins a cluster, it expects a successfully elected master. If too few master-eligible nodes are present, or discovery and voting configuration prevents a quorum, the cluster cannot elect a master and might not start or accept membership.
Common causes include an insufficient number of master-eligible nodes, network partitions that hide masters from other nodes, and misconfigured discovery or cluster bootstrapping settings.
Until a master is elected, cluster-state changes cannot proceed and dependent nodes remain blocked.