The task with id doesn’t exist – How to solve this Elasticsearch error

Average Read Time

2 Mins

The task with id doesn’t exist – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” the task with id doesn’t exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task and persistent.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “the task with id {} doesn’t exist”classname  is PersistentTasksClusterService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

public ClusterState execute(ClusterState currentState) {
 PersistentTasksCustomMetadata.Builder tasksInProgress = builder(currentState);
 if (tasksInProgress.hasTask(id)) {
 return update(currentState; tasksInProgress.removeTask(id));
 } else {
 throw new ResourceNotFoundException("the task with id {} doesn't exist"; id);
 }
 } 
 @Override
 public void onFailure(String source; Exception e) {

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content