Source shard is not marked yet as relocating to request targetNode – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch attempts to relocate a shard to a target node, but the source shard is not yet marked as relocating. This could be due to a delay in the cluster state update or a network issue. To resolve this, you can try manually relocating the shard, ensure the cluster state is updated, or check for network connectivity issues between the nodes. Also, ensure that the target node has enough resources to handle the shard.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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, indices, request, shard, source.

Log Context

Log “source shard is not marked yet as relocating to [” + request.targetNode() + “]” class name is PeerRecoverySourceService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 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; task; shard);
 logger.trace(
 "[{}][{}] starting recovery to {}";

 

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?