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.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | performance, configuration, recovery |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| Maximum node concurrent recoveries | Integer | 2 |
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.
cluster.routing.allocation.node_concurrent_recoveries is 12. Recommended maximum: 2.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
PUT _cluster/settings
{
"persistent": {
"cluster.routing.allocation.node_concurrent_recoveries": 2
}
}
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
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.