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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Rollup indexer ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indexer, plugin and task.

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) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content