---
title: Coordinating node restarted
description: Describes what AutoOps detects and surfaces with the Coordinating node restarted insight: A coordinating node restarted and rejoined the cluster.
url: https://www.elastic.co/docs/reference/autoops-insights/elasticsearch/coordinating_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
---

# Coordinating node restarted
A coordinating node restarted and rejoined the cluster. This insight is mainly informational for change tracking and post-incident timelines.
<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.

### Coordinating node rejoined the cluster


#### What was detected

A coordinating 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 coordinating node restarts, clients pinned to that host might see brief connection errors until they retry other coordinators. After rejoin, the node resumes request fan-out and aggregation.
Planned rolling restarts are usually low risk if enough coordinators remain available during the restart.

## Guide

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