Failed to index items into ILM history index – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-8.2

Briefly, this error occurs when Elasticsearch is unable to index items into the Index Lifecycle Management (ILM) history index. This could be due to insufficient permissions, a full disk, or a misconfigured ILM policy. To resolve this issue, 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 the Elasticsearch cluster and ensure it’s functioning properly.

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

Log Context

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


            public void afterBulk(long executionId; BulkRequest request; Throwable failure) {
                long items = request.numberOfActions();
                logger.error(new ParameterizedMessage("failed to index {} items into ILM history index"; items); failure);
        }; "ilm-history-store")