Low concurrent recoveries
Node concurrent recoveries is below the recommended value. Shard recovery after node loss or corruption might be unnecessarily slow.
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 minimum: 2.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
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.
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.