The task with id and allocation 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 and allocation id doesn’t exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task, allocation 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 {} and allocation id {} doesn’t exist”classname  is PersistentTasksClusterService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (tasksInProgress.hasTask(taskId)) {
 logger.warn("trying to update state on task {} with unexpected allocation id {}"; taskId; taskAllocationId);
 } else {
 logger.warn("trying to update state on non-existing task {}"; taskId);
 }
 throw new ResourceNotFoundException("the task with id {} and allocation id {} doesn't exist"; taskId; taskAllocationId);
 }
 } 
 @Override
 public void onFailure(String source; Exception e) {

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content