Failed to list shard on node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.3-1.3

Briefly, this error occurs when Elasticsearch is unable to list the shards on a specific node. This could be due to network issues, node failure, or insufficient permissions. To resolve this, you can try restarting the node, checking the network connection, or ensuring the user has the correct permissions. If the node is consistently failing, consider relocating the shards to a different node.

This guide will help you check for common problems that cause the log ” {}: failed to list shard {} on node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node and shard.

Log Context

Log “{}: failed to list shard {} on node [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             Throwable cause = ExceptionsHelper.unwrapCause(failure);
            if (cause instanceof ConnectTransportException) {
            // we log warn here. debug logs with full stack traces will be logged if debug logging is turned on for TransportNodeListGatewayStartedShards
            logger.warn("{}: failed to list shard {} on node [{}]"; failure; shard.shardId(); actionType; failure.nodeId());

    private Map buildShardStores(DiscoveryNodes nodes; MutableShardRouting shard) {
        Map shardStores = cachedStores.get(shard.shardId());


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?