---
title: Data Node Restarted
description: Describes what AutoOps detects and surfaces with the Data Node Restarted insight: A data node has rejoined the cluster after a restart.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/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 has 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://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/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 was rejoined to cluster


#### What was detected

Nodes: - `es-data-01`

#### Recommendations

No recommendations are linked to this insight.

#### Background and impact

Data node was rejoined to cluster.