Shard state info found – How to solve this OpenSearch error

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when OpenSearch cannot find the shard state information. This could be due to a corrupted index or a network partition that prevents the node from communicating with the cluster. To resolve this issue, you can try to restore the index from a backup, recreate the index, or check the network connectivity between the nodes. If the problem persists, consider increasing the cluster’s fault tolerance by adding more replicas.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” {} shard state info found: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: shard.

Log Context

Log “{} shard state info found: [{}]” classname is
We extracted the following from OpenSearch source code for those seeking an in-depth context :


                logger.debug("{} shard state info found: [{}]"; shardId; shardStateMetadata);
                String allocationId = shardStateMetadata.allocationId != null ? shardStateMetadata.allocationId.getId() : null;
                final IndexShard shard = indicesService.getShardOrNull(shardId);
                return new NodeGatewayStartedShards(


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?

Get expert answers on Elasticsearch/OpenSearch