Failed to list shard on node – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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 ” 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());


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content