Cancelled – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-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 an Elasticsearch operation is cancelled due to a timeout or an explicit user cancellation. This could be due to a long-running query or a heavy indexing operation. To resolve this issue, you can increase the timeout limit, optimize your queries or indexing operations to run faster, or increase the resources of your Elasticsearch cluster to handle heavier loads. Additionally, ensure that your cluster is not overloaded with too many operations at once.

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 ” cancelled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: search.

Log Context

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

 IndexSearcher searcher = new IndexSearcher(context.searcher().getIndexReader()) {
 public TermStatistics termStatistics(Term term; int docFreq; long totalTermFreq) throws IOException {
 if (context.isCancelled()) {
 throw new TaskCancelledException("cancelled");
 try {
 TermStatistics ts = super.termStatistics(term; docFreq; totalTermFreq);
 if (ts != null) {


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?

Get expert answers on Elasticsearch/OpenSearch