Source node does not have the shard listed in its state as allocated on the node – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” source node does not have the shard listed in its state as allocated on the node ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery, source, shard, indices and node.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “source node does not have the shard listed in its state as allocated on the node”classname  is RecoverySourceHandler.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final IndexShardRoutingTable routingTable = shard.getReplicationGroup().getRoutingTable();
 ShardRouting targetShardRouting = routingTable.getByAllocationId(request.targetAllocationId());
 if (targetShardRouting == null) {
 logger.debug("delaying recovery of {} as it is not listed as assigned to target node {}"; request.shardId();
 request.targetNode());
 throw new DelayRecoveryException("source node does not have the shard listed in its state as allocated on the node");
 }
 assert targetShardRouting.initializing() : "expected recovery target to be initializing but was " + targetShardRouting;
 retentionLeaseRef.set(
 shard.getRetentionLeases().get(ReplicationTracker.getPeerRecoveryRetentionLeaseId(targetShardRouting)));
 }; shardId + " validating recovery target ["+ request.targetAllocationId() + "] registered ";

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content