The task with id ” + id + ” and allocation id ” + allocationId + ” not found – 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 ” + id + ” and allocation id ” + allocationId + ” not found ” 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 [” + id + “] and allocation id [” + allocationId + “] not found”classname  is PersistentTasksClusterService.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

logger.warn("The task [{}] with id [{}] was found but it has a different allocation id [{}]; status is not updated";
 PersistentTasksCustomMetadata.getTaskWithId(currentState; id).getTaskName(); id; allocationId);
 } else {
 logger.warn("The task [{}] wasn't found; status is not updated"; id);
 }
 throw new ResourceNotFoundException("the task with id [" + id + "] and allocation id [" + allocationId + "] not found");
 }
 } 
 @Override
 public void onFailure(String source; Exception e) {

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content