Recovery was cancelled – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” recovery was cancelled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: recovery and indices.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “recovery was cancelled”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public void cancel() {
 isCancelled = true;
 if (onGoingRetryableActions.isEmpty()) {
 final RuntimeException exception = new CancellableThreads.ExecutionCancelledException("recovery was cancelled");
 // Dispatch to generic as cancellation calls can come on the cluster state applier thread
 threadPool.generic().execute(() -> {
 for (RetryableAction action : onGoingRetryableActions.values()) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content