Source shard ” + routingEntry + ” is not an active primary – How to solve this Elasticsearch error

Average Read Time

2 Mins

Source shard ” + routingEntry + ” is not an active primary – 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 ” + routingEntry + ” is not an active primary ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery, routing, source, shard and indices.

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 [” + routingEntry + “] is not an active primary”classname  is PeerRecoverySourceService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

final IndexShard shard = indexService.getShard(request.shardId().id()); 
 final ShardRouting routingEntry = shard.routingEntry(); 
 if (routingEntry.primary() == false || routingEntry.active() == false) {
 throw new DelayRecoveryException("source shard [" + routingEntry + "] is not an active primary");
 } 
 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 {}";

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content