---
title: Data node restarted
description: Describes what AutoOps detects and surfaces with the Data node restarted insight: A data node rejoined the cluster after a restart.
url: https://www.elastic.co/docs/reference/autoops-insights/elasticsearch/data_node_restarted
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# 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.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://www.elastic.co/docs/reference/autoops-insights/elasticsearch).
</note>


## Insight details


| Field     | Value                                  |
|-----------|----------------------------------------|
| Component | Elasticsearch                          |
| Severity  | Low                                    |
| Scope     | Cluster                                |
| Domains   | performance, node-lifecycle, stability |


## Example: What you might see in AutoOps

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.

### Data node rejoined the cluster


#### What was detected

A data node rejoined the cluster: es-data-01.

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="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.
</dropdown>


#### Background and impact

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.

## Guide

[Full Cluster restart and rolling restart procedures](https://docs-edge.elastic.dev/docs/deploy-manage/maintenance/start-stop-services/full-cluster-restart-rolling-restart-procedures)