Loading

Cluster Concurrent Rebalance High

Cluster concurrent rebalance is set above the recommended value, so many shards might relocate at the same time. Each move consumes disk and network on both source and destination nodes.

Note

For a complete list of insights, refer to AutoOps insights.

Field Value
Component Elasticsearch
Severity Medium
Scope Cluster
Domains performance, shard-allocation

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 cluster concurrent rebalance 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 rebalance 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 could cause performance degradation due to disk and network load. This setting determines the maximum number of shards the cluster can move at any one time to rebalance the distribution of shards across the nodes, obeying any existing shard allocation rules such as allocation filtering and forced awareness. When shards are moved, resources are required on both nodes — the one sending the shard and the one receiving it. If the cluster concurrent rebalance is high, the cluster could use up too many resources at once when moving shards.