Unable to find index in cluster state – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 find index in cluster state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, shard, index.

Log Context

Log “Unable to find index in cluster state”classname  is RemoveCorruptedShardDataCommand.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

shardId = Objects.requireNonNull(shardIdOption.value(options); "Shard ID is required");
 indexMetadata = clusterState.metadata().index(indexName);
 if (indexMetadata == null) {
 throw new ElasticsearchException("Unable to find index in cluster state");
 final IndexSettings indexSettings = new IndexSettings(indexMetadata; settings);
 final Index index = indexMetadata.getIndex();
 final ShardId shId = new ShardId(index; shardId);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content