Requested shutdown of indexer for job getJobId – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch attempts to shut down an indexer for a specific job, identified by “getJobId”. This could be due to a variety of reasons such as a manual shutdown request, an error in the job, or system resource constraints. To resolve this issue, you can check the job logs for any errors, ensure that the system has sufficient resources, or restart the Elasticsearch service. If the problem persists, consider reviewing the job’s configuration or the data it’s processing for potential issues.

This guide will help you check for common problems that cause the log ” Requested shutdown of indexer for job [” + getJobId() + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, indexer, indexing.

Log Context

Log “Requested shutdown of indexer for job [” + getJobId() + “]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            case STOPPED:
                return false;

            case ABORTING:
      "Requested shutdown of indexer for job [" + getJobId() + "]");
                return false;

                // Anything other than indexing; aborting or stopping is unanticipated


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?