---
title: Loaded Coordinating Nodes
description: Describes what AutoOps detects and surfaces with the Loaded Coordinating Nodes insight: CPU or load is noticeably higher on some coordinating nodes than on others in the same role.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/loaded_coordinating_nodes
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
---

# Loaded Coordinating Nodes
CPU or load is noticeably higher on some coordinating nodes than on others in the same role. Uneven coordinating load can bottleneck search and bulk requests and lead to timeouts on the busiest nodes.
<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  | Medium                                    |
| Scope     | Node                                      |
| Domains   | performance, search, resource-utilization |


## Customization settings

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to [AutoOps event settings](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/ec-autoops-event-settings) for details.
The default customization settings are:

| Setting                                 | Type    | Default |
|-----------------------------------------|---------|---------|
| Loaded node load percent above baseline | Integer | 180     |
| Successive samplings to trigger         | Integer | 3       |
| The minimum value to consider as high   | Integer | 1       |


## 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.

### Some coordinating nodes are more loaded than others: `es-data-01`


#### What was detected

The affected node/s are: `es-data-01` and `es-data-02` High search activity indices:`logs-prod-000045` High indexing activity indices:`logs-prod-000045`

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Restart coordinating node">
  **Condition**: Shown when coordinating node CPU load is unbalanced.Restart the coordinating node (`es-data-01`) to clear stuck work, free memory, and reshuffle client connections.
</dropdown>


#### Background and impact

Impact: This might cause a bottleneck to form and reduce search and indexing performance.
The load on some coordinating nodes is unbalanced. The CPU and load on some coordinating nodes is higher than on others.
This can be caused by applications that are not load balancing correctly across the coordinating nodes. A saturated coordinating node could ultimately lead to queries timing out.