Shard rebalancing restricted
Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
ECH
Generally available
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
Shard rebalancing is turned off or restricted, so the cluster cannot move shards off overloaded disks or onto newly added nodes within your allocation rules. 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.
cluster.routing.rebalance.enable is not set to all. Shard rebalancing is turned off or limited.
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.
Shard rebalancing is how the master moves shards to improve balance across data nodes, for example from high disk utilization to lower utilization, or onto a newly added node.
Operators sometimes turn off rebalancing during maintenance. While it stays off, the cluster cannot correct skew from growth, node addition, or uneven indexing. Overloaded nodes keep more load than they should.
Re-enable rebalancing (all) when maintenance is done so the master can optimize placement within your allocation filters and disk watermarks.