Source has canceled the recovery – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.16-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 the source node that was transferring data to the target node during shard recovery process cancels the operation. This could be due to the source node going down, network issues, or the recovery process taking too long. To resolve this, you can try restarting the source node if it’s down, checking and fixing network connectivity issues, or increasing the recovery timeout settings in Elasticsearch. Additionally, ensure that your cluster has enough resources to handle 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 ” source has canceled the recovery ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery, source, indices.

Log Context

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

 if (cause instanceof CancellableThreads.ExecutionCancelledException) {
 // this can also come from the source wrapped in a RemoteTransportException
 new RecoveryFailedException(request; "source has canceled the recovery"; cause);
 if (cause instanceof RecoveryEngineException) {


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?