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

# Master Node Restarted
A master-eligible node has rejoined the cluster after a restart. Brief master elections can occur during rejoin and might affect cluster coordination.
<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.

### Master node was rejoined to cluster


#### What was detected

Nodes: - `es-data-01`

#### Recommendations

No recommendations are linked to this insight.

#### Background and impact

Master node was rejoined to cluster.