Failed to retry recovery – 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 fails to recover data from a shard after a node failure or during a shard relocation process. This could be due to insufficient disk space, network issues, or corrupted data. To resolve this, you can try increasing the disk space, checking the network connectivity, or restoring the data from a backup. Additionally, you can also try to manually reroute the shard using the cluster reroute API or increase the “indices.recovery.max_bytes_per_sec” setting to speed up the recovery process.

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 ” failed to retry recovery ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery, indices.

Log Context

Log “failed to retry recovery” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 cancelRecovery(newRecoveryTarget.recoveryId(); "recovery cancelled during reset");
 return null;
 } catch (Exception e) {
 // fail shard to be safe
 oldRecoveryTarget.notifyListener(new RecoveryFailedException(oldRecoveryTarget.state(); "failed to retry recovery"; e); true);
 return null;
 }  public RecoveryTarget getRecoveryTarget(long id) {


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?

Get expert answers on Elasticsearch/OpenSearch