Source shard is not marked yet as relocating to ” + request.targetNode() + ” – 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 shard is not marked yet as relocating to ” + request.targetNode() + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery, source, shard, indices and request.

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 shard is not marked yet as relocating to [” + request.targetNode() + “]”classname  is PeerRecoverySourceService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (request.isPrimaryRelocation() && (routingEntry.relocating() == false ||
 routingEntry.relocatingNodeId().equals(request.targetNode().getId()) == false)) {
 logger.debug("delaying recovery of {} as source shard is not marked yet as relocating to {}";
 request.shardId(); request.targetNode());
 throw new DelayRecoveryException("source shard is not marked yet as relocating to [" + request.targetNode() + "]");
 } 
 RecoverySourceHandler handler = ongoingRecoveries.addNewRecovery(request; shard);
 logger.trace("[{}][{}] starting recovery to {}"; request.shardId().getIndex().getName(); request.shardId().id();
 request.targetNode());

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content