Operation was cancelled reason ” + reason + ” – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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

Log Context

Log “operation was cancelled reason [” + reason + “]”classname  is CancellableThreads.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 if (onCancel != null) {
 onCancel.onCancel(reason; beforeCancelException);
 }
 // fallback to the default exception
 final RuntimeException cancelExp = new ExecutionCancelledException("operation was cancelled reason [" + reason + "]");
 if (beforeCancelException != null) {
 cancelExp.addSuppressed(beforeCancelException);
 }
 throw cancelExp;
 }

 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content