Recovery was canceled reason ” + reason + ” – 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 canceled reason ” + reason + ” ” 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 canceled reason [” + reason + “]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

cancellableThreads.setOnCancel((reason; beforeCancelEx) -> {
 final RuntimeException e;
 if (shard.state() == IndexShardState.CLOSED) { // check if the shard got closed on us
 e = new IndexShardClosedException(shard.shardId(); "shard is closed and recovery was canceled reason [" + reason + "]");
 } else {
 e = new CancellableThreads.ExecutionCancelledException("recovery was canceled reason [" + reason + "]");
 if (beforeCancelEx != null) {
 IOUtils.closeWhileHandlingException(releaseResources; () -> future.onFailure(e));


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content