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

 
 

search

Overview

Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET API request to the _search endpoint. The search query can either be provided in query string or through a request body.

Examples

When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.

GET my_documents/_search

A JSON object is returned in response to a search query. A 200 response code means the request was completed successfully.

{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}

Notes and good things to know

  • Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
  • There are two phases of search: the query phase and the fetch phase.
  • In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list. 
  • In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
  • A coordinating node needs enough memory and CPU in order to handle the fetch phase.
 
 

 
 

Log Context

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

Map stats = new HashMap<>();
 IndexSearcher searcher = new IndexSearcher(context.searcher().getIndexReader()) {
 @Override
 public TermStatistics termStatistics(Term term; int docFreq; long totalTermFreq) throws IOException {
 if (context.isCancelled()) {
 throw new TaskCancelledException("cancelled");
 }
 TermStatistics ts = super.termStatistics(term; docFreq; totalTermFreq);
 if (ts != null) {
 stats.put(term; ts);
 }

 

"With Opster, we’ve been able to reduce our hardware costs by over $4 million."

Arpit Ghiya

Senior Lead SRE at Coupa

Read Case Study

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Related Articles

How to Easily Upgrade Elasticsearch Versions

How to Handle Recurring RED Status

Coupa Reduced Elasticsearch Costs by 60%

Skip to content