Rollup job params getConfig getId created – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when there’s an issue with the parameters of a Rollup job in Elasticsearch. Rollup jobs are used to summarize and store historical data, which can be used for analysis. The error might be due to incorrect job configuration, invalid job ID, or issues with the creation of the job. To resolve this, ensure the job ID is correct and the job configuration is valid. If the issue persists, try recreating the job. Also, check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” Rollup job [” + params.getConfig().getId() + “] created. ” 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 [” + params.getConfig().getId() + “] created.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            // Note that while the task is added to the scheduler here; the internal state will prevent
            // it from doing any work until the task is "started" via the StartJob api

  "Rollup job [" + params.getConfig().getId() + "] created.");

        protected AllocatedPersistentTask createTask(
            long id;