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

Opster Team

August-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when there’s an attempt to stop a Rollup Job in Elasticsearch, but the system is unable to do so due to some internal issues. This could be due to the job being in a state that doesn’t allow it to be stopped, or due to a system error. To resolve this issue, you can try to manually stop the job using the Rollup API. If that doesn’t work, check the job’s state and ensure it’s in a stoppable state. If the problem persists, consider restarting the Elasticsearch node or checking for system errors.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Cannot stop 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 stop 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 :

 break;  default:
 listener.onFailure(new ElasticsearchException("Cannot stop task for Rollup Job [" + job.getConfig().getId() + "] because"
 + " state was [" + newState + "]"));


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?