Cannot start task for Rollup Job job getConfig getId because – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch is unable to start a rollup job due to a configuration issue or a system resource constraint. The rollup job ID mentioned in the error message can help identify the problematic job. To resolve this, you can check the configuration of the rollup job for any inconsistencies. If the configuration is correct, ensure that the system has enough resources (CPU, memory, disk space) to execute the job. If the issue persists, consider breaking the job into smaller tasks or increasing the system resources.

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

Log Context

Log “Cannot start task for Rollup Job [” + job.getConfig().getId() + “] because” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public synchronized void start(ActionListener listener) {
 final IndexerState prevState = indexer.getState();
 if (prevState != IndexerState.STOPPED) {
 // fails if the task is not STOPPED
 listener.onFailure(new ElasticsearchException("Cannot start task for Rollup Job [" + job.getConfig().getId() + "] because"
 + " state was [" + prevState + "]"));
 }  final IndexerState newState = indexer.start();


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?