Received shard failed for – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 2.3-2.3

Briefly, this error occurs when Elasticsearch encounters an issue with a specific shard, which could be due to a variety of reasons such as hardware failure, network issues, or data corruption. To resolve this, you can try to restart the Elasticsearch node, check for hardware or network issues, or use the Elasticsearch shard reroute API to manually allocate the shard. If data corruption is the issue, you may need to restore the data from a backup.

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

Log Context

Log “{} received shard failed for {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    private final ShardFailedClusterStateHandler shardFailedClusterStateHandler = new ShardFailedClusterStateHandler();

    private void handleShardFailureOnMaster(final ShardRoutingEntry shardRoutingEntry) {
        logger.warn("{} received shard failed for {}"; shardRoutingEntry.failure; shardRoutingEntry.shardRouting.shardId(); shardRoutingEntry);
                "shard-failed (" + shardRoutingEntry.shardRouting + "); message [" + shardRoutingEntry.message + "]";


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?