Shard is no longer relocating – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.16-8.9

Briefly, this error occurs when a shard that was in the process of relocating to another node in the Elasticsearch cluster has completed its relocation or the relocation process was interrupted. This could be due to network issues, node failure, or manual intervention. To resolve this issue, you can check the cluster health and individual node status. If there are network issues, fix them. If a node has failed, you may need to restart it or add a new node. If the relocation was stopped manually, you may need to restart it if necessary.

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” class name is 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(


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?