Log Rollup indexer – How To Solve Related Issues

Log Rollup indexer – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Rollup indexer” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: indexer, plugin, task.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”Rollup indexer [” classname is RollupJobTask.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

      * This tries to remove the job from the scheduler; and potentially any other
     * cleanup operations in the future
    synchronized void shutdown() {
        try {
            logger.info("Rollup indexer [" + job.getConfig().getId() + "] received abort request; stopping indexer.");
            schedulerEngine.remove(SCHEDULE_NAME + "_" + job.getConfig().getId());
        } catch (Exception e) {


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Can an Elasticsearch rollup job dynamically create indexes like Logstash does? -views 0.57 K ,score 2

Github Issue Number 32446  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now