Unable to index the following ILM history itemsn – 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 ” Unable to index the following ILM history itemsn ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and plugin.

Log Context

Log “unable to index the following ILM history items:n{}” classname is ILMHistoryStore.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                 logger.warn("failed to create ILM history store index prior to issuing bulk request"; ex);
                        indexCreated.get(2; TimeUnit.MINUTES);
                    } catch (Exception e) {
                        logger.warn(new ParameterizedMessage("unable to index the following ILM history items:\n{}";
                                .filter(dwr -> (dwr instanceof IndexRequest))
                                .map(dwr -> ((IndexRequest) dwr))


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?

Analyze your cluster & get personalized recommendations

Skip to content