Failed to queue ILM history item in index %s %s – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.4-8.6

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 is unable to queue an Index Lifecycle Management (ILM) history item in a specific index. This could be due to insufficient disk space, a configuration issue, or a problem with the ILM policy. To resolve this issue, you can check and free up disk space, review and correct the ILM policy, or check the Elasticsearch configuration for any errors. Additionally, ensure that the Elasticsearch cluster is healthy and functioning properly.

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 queue ILM history item in index [%s]: [%s] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, queue, plugin.

Log Context

Log “failed to queue ILM history item in index [%s]: [%s]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        } catch (IOException exception) {
            logger.error(() -> format("failed to queue ILM history item in index [%s]: [%s]"; ILM_HISTORY_DATA_STREAM; item); exception);

    public void close() {


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?