Failed add ILM history item to queue for index – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.15

Briefly, this error occurs when Elasticsearch is unable to add an Index Lifecycle Management (ILM) history item to the queue for a specific index. This could be due to insufficient resources, a configuration issue, or a problem with the ILM policy. To resolve this issue, you can try increasing the system resources, checking the ILM policy for any errors, or reconfiguring the ILM settings. If the problem persists, consider disabling the ILM history index or increasing its size limit.

This guide will help you check for common problems that cause the log ” failed add ILM history item to queue for index [{}]: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: queue, index, plugin.

Log Context

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

            //  see:
            threadPool.executor(ThreadPool.Names.GENERIC).execute(() -> {
                try {
                } catch (Exception e) {
                    logger.error(new ParameterizedMessage("failed add ILM history item to queue for index [{}]: [{}]";
                        ILM_HISTORY_DATA_STREAM; item); e);
        } catch (IOException exception) {
            logger.error(new ParameterizedMessage("failed to queue ILM history item in index [{}]: [{}]";


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?