No shard available for – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch is unable to find a shard for a specific operation. This could be due to a number of reasons such as the shard being relocated, the node being down, or network issues. To resolve this issue, you can try the following: 1) Check the health of your cluster and ensure all nodes are up and running. 2) Verify the network connectivity between nodes. 3) If the shard is being relocated, wait for the process to complete. 4) If the issue persists, consider increasing the number of replicas for your index.

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

Log Context

Log “No shard available for [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final ShardRouting shardRouting = shardIt.nextOrNull();
 if (shardRouting == null) {
 Exception failure = lastFailure;
 if (failure == null || isShardNotAvailableException(failure)) {
 failure = new NoShardAvailableActionException(null; LoggerMessageFormat.format("No shard available for [{}]";
 internalRequest.request()); failure);
 } else {
 logger.debug(() -> new ParameterizedMessage("{}: failed to execute [{}]"; null; internalRequest.request()); failure);


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?