Rollup job job getConfig getId failed with an exception – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to retrieve the configuration details of a specific rollup job due to an internal exception. This could be due to issues like incorrect job ID, network problems, or insufficient permissions. To resolve this, ensure the job ID is correct, check the network connectivity, and verify that the user has the necessary permissions to access the rollup job. Also, check the Elasticsearch logs for any specific exceptions or errors that might provide more insight into the problem.

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

Log Context

Log “Rollup job [” + job.getConfig().getId() + “] failed with an exception: ” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            client.admin().indices().refresh(new RefreshRequest(jobConfig.getRollupIndex()); refreshResponseActionListener);

        protected void onFailure(Exception exc) {
            logger.warn("Rollup job [" + job.getConfig().getId() + "] failed with an exception: "; exc);

        protected void onAbort() {