Coordinating node restarted
A coordinating node restarted and rejoined the cluster. This insight is mainly informational for change tracking and post-incident timelines.
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 coordinating 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 coordinating node restarts, clients pinned to that host might see brief connection errors until they retry other coordinators. After rejoin, the node resumes request fan-out and aggregation.
Planned rolling restarts are usually low risk if enough coordinators remain available during the restart.