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

# Low concurrent recoveries
Node concurrent recoveries is below the recommended value. Shard recovery after node loss or corruption might be unnecessarily slow.
<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 below the recommended minimum


#### What was detected

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

#### Recommendations

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

<dropdown title="Increase concurrent recoveries limit">
  **Condition**: Always shown for this insight.`cluster.routing.allocation.node_concurrent_recoveries` limits how many shards recover to one node at once. Raise it with the action below to speed recovery; lower values reduce overload risk but take longer.
  ```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

Following node loss or data corruption, the master recovers shards across the network. The `node_concurrent_recoveries` setting limits how many recoveries can run at once on each node.
If the value is below the recommended minimum, recovery might proceed slower than necessary. Primary and replica shards might not restore as quickly, which increases exposure if further failures occur before recovery completes.

## Guide

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