: shard is no longer relocating – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when a shard is unable to be relocated to a new node. This can happen when a node goes down or a cluster is being reconfigured. The solution to this error is to check the status of the node and cluster, ensure there is enough disk space, and to manually relocate the shard if necessary.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” : shard is no longer relocating ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index.

Log Context

Log “: shard is no longer relocating”classname  is IndexShard.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

* that we concurrently end up here and therefore have to protect that we do not mark the shard as relocated when its shard routing
 * says otherwise.
 if (shardRouting.relocating() == false) {
 throw new IllegalIndexShardStateException(shardId; IndexShardState.STARTED; ": shard is no longer relocating " + shardRouting);
 if (primaryReplicaResyncInProgress.get()) {
 throw new IllegalIndexShardStateException(


See how you can use AutoOps to resolve issues

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Skip to content