Data node restarted
A data node rejoined the cluster after a restart. Shard recovery and rebalance activity might run for a while on that node and its peers.
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 data 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 data node restarts, its shards are unavailable until the node rejoins and recovery completes. Peer nodes might serve replica shards during the outage.
After rejoin, shard recovery and rebalancing can increase disk and network activity on the node and its peers until allocation stabilizes.