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


#### What was detected

A master-eligible 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 master-eligible node restarts, it is temporarily absent from master elections. The cluster might elect a new master if the active master was on the restarted node. Brief coordination delays are possible during rejoin.
Planned rolling restarts are usually low risk if quorum is maintained throughout.

## Guide

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