Rollup indexer – How to solve related issues

Average Read Time

2 Mins

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 run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Rollup indexer [” classname is
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 {
  "Rollup indexer [" + job.getConfig().getId() + "] received abort request; stopping indexer.");
            schedulerEngine.remove(SCHEDULE_NAME + "_" + job.getConfig().getId());
        } catch (Exception e) {


Run the Check-Up to get a customized report like this:

Analyze your cluster