Rollup indexer job getConfig getId received abort request stopping indexer – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when an Elasticsearch rollup job receives an abort request while it’s running. This could be due to a manual stop request or an internal issue. To resolve this, you can try restarting the rollup job. If the problem persists, check the Elasticsearch logs for any underlying issues that might be causing the abort request. Also, ensure that the Elasticsearch cluster has sufficient resources to handle the rollup job. If necessary, you may need to optimize your rollup configuration or increase the resources of your Elasticsearch cluster.

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

Log Context

Log “Rollup indexer [” + job.getConfig().getId() + “] received abort request; stopping 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) {