---
title: Node Concurrent Recoveries High
description: Describes what AutoOps detects and surfaces with the Node Concurrent Recoveries High insight: The node concurrent recoveries setting is above the recommended value.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/node_concurrent_recoveries_high
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
---

# Node Concurrent Recoveries High
The node concurrent recoveries setting is above the recommended value. More concurrent recoveries increase network and disk load and can hurt indexing and search on affected 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     | Cluster                              |
| Domains   | performance, configuration, recovery |


## 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 |
|------------------------------------|---------|---------|
| Maximum node concurrent recoveries | Integer | 2       |


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

### The node concurrent recoveries setting is set to a higher value than recommended


#### What was detected

The current concurrent recoveries setting is set to: 12.
The recommended setting is: 12.

#### Recommendations

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

<dropdown title="Decrease concurrent recoveries limit">
  **Condition**: Always shown for this insight.High `cluster.routing.allocation.node_concurrent_recoveries` can overload nodes during recovery. Lower it with the action below to reduce cluster pressure.
  ```json

  {
    "persistent": {
      "cluster.routing.allocation.node_concurrent_recoveries": 12
    }
  }
  ```

  <note>
    Requires the `manage cluster` privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
  </note>
</dropdown>


#### Background and impact

Impact: This might cause performance degradation due to disk and network load.
The concurrent recoveries setting governs the number of shards that can be recovered across the network from other nodes (usually replica shards). The number of concurrent recoveries is limited (by default it is set to 2) to prevent the network between nodes from becoming overloaded.
Increasing this setting above the default value might cause shard movements to have a performance impact on other activity in your cluster, but might not make shard movements complete noticeably sooner.