Loading local shard state info – 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 encounters issues while trying to load shard state information from the local disk. This could be due to disk I/O problems, corrupted shard data, or insufficient permissions. To resolve this, you can try the following: 1) Check and fix any disk I/O issues. 2) Restore the shard from a backup if the data is corrupted. 3) Ensure OpenSearch has the necessary permissions to access the shard files. 4) If the shard is not critical, you can delete and recreate it. Always ensure to have a backup before performing any operation.

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 ” {} loading local shard state info ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: shard.

Log Context

Log “{} loading local shard state info” classname is TransportNodesListGatewayStartedShards.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :

    protected NodeGatewayStartedShards nodeOperation(NodeRequest request) {
        try {
            final ShardId shardId = request.getShardId();
            logger.trace("{} loading local shard state info"; shardId);
            ShardStateMetadata shardStateMetadata = ShardStateMetadata.FORMAT.loadLatestState(


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