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 analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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

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


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content