Master-eligible node restarted
A master-eligible node rejoined the cluster after a restart. Brief master elections can occur during rejoin and might affect cluster coordination.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Cluster |
| Domains | performance, node-lifecycle, stability |
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.
A master-eligible node rejoined the cluster: es-data-01.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Investigate node restart
Condition: Always shown for this insight.
Review Elasticsearch and host logs for es-data-01 around the restart time for out-of-memory errors, garbage collection failures, fatal exceptions, or planned maintenance. Confirm cluster health is green and recovery has finished.
When a master-eligible node restarts, it is temporarily absent from master elections. The cluster might elect a new master if the active master was on the restarted node. Brief coordination delays are possible during rejoin.
Planned rolling restarts are usually low risk if quorum is maintained throughout.