Sending failed shard for . indexUUID . reason – How to solve related issues

Sending failed shard for . indexUUID . reason – 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 ” Sending failed shard for . indexUUID . reason ” 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, index 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 “{} sending failed shard for {}; indexUUID [{}]; reason [{}]” classname is ShardStateAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         }
        shardFailed(shardRouting; indexUUID; reason; masterNode);
    }

    public void shardFailed(final ShardRouting shardRouting; final String indexUUID; final String reason; final DiscoveryNode masterNode) throws ElasticsearchException {
        logger.warn("{} sending failed shard for {}; indexUUID [{}]; reason [{}]"; shardRouting.shardId(); shardRouting; indexUUID; reason);
        innerShardFailed(shardRouting; indexUUID; reason; masterNode);
    }

    public void resendShardFailed(final ShardRouting shardRouting; final String indexUUID; final String reason; final DiscoveryNode masterNode) throws ElasticsearchException {
        logger.trace("{} re-sending failed shard for {}; indexUUID [{}]; reason [{}]"; shardRouting.shardId(); shardRouting; indexUUID; reason);




 

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

Analyze your cluster