Before you dig into the details of this technical guide, have you tried asking OpsGPT?
You'll receive concise answers that will help streamline your Elasticsearch/OpenSearch operations.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch/ OpenSearch operation.
Before you dig into the details of this guide, have you tried asking OpsGPT? You’ll receive concise answers that will help streamline your Elasticsearch/OpenSearch operations.
Try OpsGPT now for step-by-step guidance and tailored insights into your search operation.
To easily resolve issues in your deployment, including those related to shards, and locate their root cause, try AutoOps for Elasticsearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.
Overview
Cluster shard rebalancing and allocation are often confused with each other.
Elasticsearch cluster shard allocation
This refers to the process by which any shard including new, recovered or rebalanced shards are allocated to Elasticsearch nodes. Cluster shard allocation may be temporarily disabled during maintenance in order to avoid shards from being relocated to nodes that are being restarted and may temporarily leave the cluster.
If cluster shard allocation is NOT enabled, then Elasticsearch will not be able to create new indices, recover corrupted indices or rebalance. This situation is very likely to cause data loss if not corrected quickly.
Elasticsearch cluster shard rebalancing
This refers to the process by which an Elasticsearch cluster may rebalance shards from nodes with high disk utilization (above the value of cluster.routing.allocation.disk.watermark.high) to nodes with lower disk utilisation, or redistribute shards from pre-existing nodes to a new node which has just been added to the cluster.
If cluster shard rebalancing is not enabled, then Elasticsearch will not be able to optimize disk and cpu utilization across the cluster by rebalancing shards from heavily used nodes to underused nodes.
How to resolve it
The default values are the recommended ones for both of these settings. To restore the default value run the following command:
PUT _cluster/settings
{
"transient": {
"cluster.routing.allocation.enable": "all",
"cluster.routing.rebalance.enable": "all"
}
}
