Elasticsearch Cluster Concurrent Rebalance High / Low

Elasticsearch Cluster Concurrent Rebalance High / Low

Opster Team

July 2020, Version: 1.7-8.0

Before you begin reading the explanation below, try running the free ES Health Check-Up get actionable recommendations that can improve Elasticsearch performance and prevent serious incidents. Just 2 minutes to complete and you can check your threadpools, memory, snapshots and many more


What Does it Mean

The cluster concurrent rebalance setting determines the maximum number of shards which the cluster can move to rebalance the distribution of disk space requirements across the nodes at any one time.

When moving shards, a shard rebalance is required in order to rebalance the disk usage requirements across the clusters. This rebalance uses cluster resources. Therefore, it’s advisable to reduce the concurrent rebalance setting to limit the number of shards that can be moved, so that the cluster doesn’t use up too many resources moving shards at any one time. The default value for this setting is 2. 

If, on the other hand, the concurrent rebalance setting is too low, the cluster may not be able to rebalance shards at all. This could cause some nodes to be unable to allocate shards due to full disks even if there is space available on other nodes. This could result in the cluster going yellow or red and not being able to write new data to certain indices.

How to Fix it

Check the current cluster settings.

GET _cluster/settings

If necessary, change the concurrent rebalance settings.  Remember that the default value is 2.

PUT _cluster/settings
  "transient": {
    "cluster.routing.allocation.cluster_concurrent_rebalance": 2

About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now