Loading local shard state info – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is trying to load shard state information from the local disk but encounters an issue. This could be due to a corrupted shard, insufficient disk space, or file permission issues. To resolve this, you can try to restore the shard from a backup, free up disk space, or check and correct file permissions. If the shard is corrupted and there’s no backup, you may need to delete and reindex the data. Always ensure to monitor your disk usage and regularly backup your data to prevent such issues.

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 Elasticsearch concepts: shard.

Log Context

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

    protected NodeGatewayStartedShards nodeOperation(NodeRequest request; Task task) {
        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?