Loading

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.

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.

The current concurrent recoveries setting is set to: 12.

The recommended setting is: 12.

Note

AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.

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.