No index state found ignoring – 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.

Briefly, this error message indicates that Elasticsearch is unable to find the state of a particular index. This could be due to the index being deleted, or due to a problem with the Elasticsearch cluster. To resolve this issue, you can try checking the Elasticsearch logs for more information on the root cause of the error and then take the necessary steps to address the issue. If the index has been deleted, you can try restoring it from a backup.

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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” No index state found ignoring ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “[{}] no index state found – ignoring” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     upgrade(index; indexFolderPath; indexFolderPath.resolveSibling(index.getUUID()));
                } else {
                    logger.debug("[{}] no upgrade needed - already upgraded"; indexFolderPath);
            } else {
                logger.warn("[{}] no index state found - ignoring"; indexFolderPath);



Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content