Master-eligible node disconnected
A master-eligible node disconnected from the cluster. Losing masters reduces fault tolerance and can trigger a master election.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | cluster-health, node-lifecycle, stability |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| Node disconnect timeout in seconds | Integer | 300 |
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.
Disconnected node: es-data-01 and es-data-02
Before the node disconnected, related conditions were observed:
-
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Investigate disconnected node activity
Condition: Always shown for this insight.
Review tasks, slow search logs, and indexing logs from before the disconnect to find costly requests or errors that might have caused the node to drop.
Master-eligible nodes elect the cluster master and apply cluster-state updates. Losing a master-eligible node reduces fault tolerance and can trigger a master election. If too few master-eligible nodes remain reachable, the cluster can lose quorum and become unavailable until enough nodes rejoin.
Unplanned disconnects might reflect host failure, network partitions, or resource pressure on the node. Investigate the affected node and remaining master-eligible capacity.