The task with id and allocation id doesn’t exist – Elasticsearch Error How To Solve Related Issues



The task with id and allocation id doesn’t exist – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: task, allocation, persistent.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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) {

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Deleted items appears when searching a replica shard – Elasticsearch  

Deleted items appears when searching a replica shard – Elasticsearch  



Find Configuration Errors

Analyze Now