Task was cancelled – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.17-8.9

Briefly, this error occurs when an Elasticsearch task is interrupted before it can complete. This could be due to a timeout, a manual cancellation, or a system shutdown. To resolve this issue, you can increase the timeout limit, ensure that tasks are not manually cancelled prematurely, or check for system stability to prevent unexpected shutdowns. Additionally, optimizing your queries and indices can help tasks complete more quickly, reducing the chance of cancellation.

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

Log Context

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

 protected void doExecute(Task task; final Request request; ActionListener listener) {
 ClusterState state = clusterService.state();
 logger.trace("starting to process request [{}] with cluster state version [{}]"; request; state.version());
 if (isTaskCancelled(task)) {
 listener.onFailure(new TaskCancelledException("Task was cancelled"));
 try {
 ClusterState clusterState = clusterService.state();
 DiscoveryNode healthNode = HealthNode.findHealthNode(clusterState);