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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard and index.

Log Context

Log “Trying to recover when the shard is in backup state”classname  is 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) {


See how you can use AutoOps to resolve issues

How useful 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?

Analyze your cluster & get personalized recommendations

Skip to content