Task for Rollup Job request getId not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot find the task associated with a specific Rollup Job. This could be due to the job being deleted, not yet created, or an incorrect job ID being used. To resolve this issue, you can verify the job ID, ensure the job has been created and is not deleted. If the problem persists, consider recreating the job or checking for any underlying issues with your Elasticsearch cluster that might be causing tasks to disappear or fail.

This guide will help you check for common problems that cause the log ” Task for Rollup Job [” + request.getId() + “] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, request.

Log Context

Log “Task for Rollup Job [” + request.getId() + “] not found” class name is TransportStartRollupAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  // Either the job doesn't exist (the user didn't create it yet) or was deleted after the StartAPI executed.
 // In either case; let the user know
 if (tasks.size() == 0) {
 throw new ResourceNotFoundException("Task for Rollup Job [" + request.getId() + "] not found");
 }  assert tasks.size() == 1;  boolean allStarted = tasks.stream().allMatch(StartRollupJobAction.Response::isStarted);


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?