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.
Overview
A task is an Elasticsearch operation, which can be any request performed on an Elasticsearch cluster, such as a delete by query request, a search request and so on. Elasticsearch provides a dedicated Task API for the task management which includes various actions, from retrieving the status of current running tasks to canceling any long running task.
Examples
Get all currently running tasks on all nodes of the cluster
Apart from other information, the response of the below request contains task IDs of all the tasks which can be used to get detailed information about the particular task in question.
GET _tasks
Get detailed information of a particular task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in below request
GET _tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759
Get all the current tasks running on particular nodes
GET _tasks?nodes=nodeId1,nodeId2
Cancel a task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in the below request
POST /_tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759/_cancel?pretty
Notes
- The Task API will be most useful when you want to investigate the spike of resource utilization in the cluster or want to cancel an operation.
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);
