Shard Rebalance Enable All
Shard rebalancing is turned off, so the cluster cannot move shards off overloaded disks or onto newly added nodes. Disk and CPU skew can persist until hot nodes saturate while others stay underused.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | performance, configuration, shard-allocation |
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.
No description available.
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Enable shard rebalance
Condition: Always shown for this insight.
Reset cluster.routing.rebalance.enable so primary and replica shards can rebalance across nodes.
PUT _cluster/settings
{
"transient": {
"cluster.routing.rebalance.enable": null
},
"persistent": {
"cluster.routing.rebalance.enable": null
}
}
Requires the manage cluster privilege. Requires Elasticsearch 8.0.0 or later. This action changes cluster or index configuration.
Impact: When shard rebalancing is turned off, the master node will not be able to optimize disk and CPU utilization across the cluster. Shard rebalancing refers to the process by which the master node might either move shards from a node with high disk utilization to nodes with lower utilization, or from a pre-existing node to a new node that has been added to the cluster. When cluster shard rebalancing is not enabled, the cluster will not be able to optimize disk and CPU utilization by rebalancing shards away from overloaded nodes.