Log Failing shard – How To Solve Related Issues

Log Failing shard – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “Failing shard” it’s important to understand a few problems related to Elasticsearch concepts allocation, cluster, routing, shard. See bellow important tips and explanations on these concepts

Log Context

Log”Failing shard [{}]” classname is AllocationService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     failedShardEntry.getFailure(); failedAllocations + 1; currentNanoTime; System.currentTimeMillis(); false;
                if (failedShardEntry.markAsStale()) {
                logger.warn(new ParameterizedMessage("failing shard [{}]"; failedShardEntry); failedShardEntry.getFailure());
                routingNodes.failShard(logger; failedShard; unassignedInfo; indexMetaData; allocation.changes());
            } else {
                logger.trace("{} shard routing failed in an earlier iteration (routing: {})"; shardToFail.shardId(); shardToFail);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Courier Fetch: shards failed

37.65 K 28

Failing to start shard in ElasticSearch IndexShardGatewayRecoveryException “sending failed”

  13.09 K 9


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now