Task for Rollup Job ” + request.getId() + ” not found – 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.

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: request, task and plugin.

Log Context

Log “Task for Rollup Job [” + request.getId() + “] not found”classname  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);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content