---
title: Coordinating node added
description: Describes what AutoOps detects and surfaces with the Coordinating node added insight: A coordinating-only node joined the cluster.
url: https://www.elastic.co/docs/reference/autoops-insights/elasticsearch/coordinating_node_added
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 added
A coordinating-only node joined the cluster. Dedicated coordinators can take on search and bulk coordination so data nodes focus on storage and indexing.
<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 was added to cluster


#### What was detected

A coordinating-only node joined the cluster: es-data-01.

#### Recommendations

No recommendations are linked to this insight.

#### Background and impact

Coordinating-only nodes handle client request fan-out and aggregation so data nodes can focus on storage and indexing. When a new coordinator joins, the cluster adjusts routing and connection patterns across members.
During the transition, peer nodes might see brief load shifts until allocation and routing stabilize. This pattern is normal after a planned scale-out.

## Guide

[Bootstrapping a cluster](https://docs-edge.elastic.dev/docs/deploy-manage/distributed-architecture/discovery-cluster-formation/modules-discovery-bootstrap-cluster)