Cancelled – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

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.

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?