The task with id ” + request.getId() + ” doesn’t exist – How to solve this Elasticsearch error

The task with id ” + request.getId() + ” 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 Error 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 ” + request.getId() + ” 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: request, task and plugin.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”the task with id [” + request.getId() + “] doesn’t exist”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (pTasksMeta != null && pTasksMeta.getTask(request.getId()) != null) {
  super.doExecute(task; request; listener);
  } else {
  // If we couldn't find the job in the persistent task CS; it means it was deleted prior to this call;
  // no need to go looking for the allocated task
  listener.onFailure(new ResourceNotFoundException("the task with id [" + request.getId() + "] doesn't exist"));
  } else {
  // Delegates DeleteJob to elected master node; so it becomes the coordinating node.
  // Non-master nodes may have a stale cluster state that shows jobs which are cancelled


Run the Check-Up to get a customized report like this:

Analyze your cluster