Trying to recover when the shard is in backup state – How to solve this Elasticsearch error

Trying to recover when the shard is in backup state – 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 Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Trying to recover when the shard is in backup state ” 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: shard and index.

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”Trying to recover when the shard is in backup state”classname  is StoreRecovery.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (indexShard.state() == IndexShardState.CLOSED) {
  // got closed on us; just ignore this recovery
  return false;
  }
  if (indexShard.routingEntry().primary() == false) {
  throw new IndexShardRecoveryException(shardId; "Trying to recover when the shard is in backup state"; null);
  }
  return true;
  }
 
  private ActionListener recoveryListener(IndexShard indexShard; ActionListener listener) {

 

Run the Check-Up to get a customized report like this:

Analyze your cluster