Failed to retry recovery – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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.

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) {