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

# High concurrent recoveries
Node concurrent recoveries 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.

### Node concurrent recoveries is above the recommended maximum


#### What was detected

`cluster.routing.allocation.node_concurrent_recoveries` is 12. Recommended maximum: 2.

#### 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": 2
    }
  }
  ```

  <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

The concurrent recoveries setting governs how many shards can recover across the network from other nodes (usually replica shards). By default Elasticsearch limits this to 2 to avoid overloading inter-node network.
Raising it above the recommended value can make shard movements compete with indexing and search. Moves might not complete much sooner because other bottlenecks often limit recovery speed.

## Guide

[Cluster level shard allocation routing settings](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings)