Unable to index the following ILM history items n – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.6

Briefly, this error occurs when Elasticsearch is unable to index the Index Lifecycle Management (ILM) history items. This could be due to insufficient permissions, a full disk, or a misconfigured ILM policy. To resolve this, you can check and adjust the user permissions, ensure there is enough disk space, or review and correct the ILM policy settings. Additionally, you may need to check the health of your Elasticsearch cluster and ensure it’s functioning properly.

This guide will help you check for common problems that cause the log ” unable to index the following ILM history items:n{} ” 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?