Failed to queue ILM history item in index – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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

Log Context

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

                     logger.error(new ParameterizedMessage("failed add ILM history item to queue for index [{}]: [{}]";
                        ILM_HISTORY_ALIAS; item); e);
        } catch (IOException exception) {
            logger.error(new ParameterizedMessage("failed to queue ILM history item in index [{}]: [{}]";
                ILM_HISTORY_ALIAS; item); exception);



Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content