Failed to shut down ILM history bulk processor after 10 seconds – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch’s Index Lifecycle Management (ILM) history bulk processor fails to shut down within the specified timeout period of 10 seconds. This could be due to a heavy load or a slow network. To resolve this issue, you can try increasing the timeout period, reducing the load on the Elasticsearch cluster, or optimizing your network performance. Additionally, ensure that your Elasticsearch cluster has sufficient resources (CPU, memory, disk space) to handle the workload.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” failed to shut down ILM history bulk processor after 10 seconds ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, bulk.

Log Context

Log “failed to shut down ILM history bulk processor after 10 seconds” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    public void close() {
        try {
            processor.awaitClose(10; TimeUnit.SECONDS);
        } catch (InterruptedException e) {
            logger.warn("failed to shut down ILM history bulk processor after 10 seconds"; e);

    public void setIlmHistoryEnabled(boolean ilmHistoryEnabled) {


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?

Get expert answers on Elasticsearch/OpenSearch