received shard failed for shard id – How to solve related issues

Average Read Time

2 Mins

received shard failed for shard id – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” received shard failed for shard id ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster and shard.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 + "]";


Run the Check-Up to get a customized report like this:

Analyze your cluster