Source shard ” + routingEntry + ” is not an active primary – Elasticsearch Error How To Solve Related Issues


Source shard ” + routingEntry + ” is not an active primary – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 {}";

 

Optimize Elasticsearch Performance

Try The Tool