No primary shards available for shard shard – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.2-8.9

Briefly, this error occurs when Elasticsearch cannot find any primary shards for the specified shard. This could be due to a network partition, a node failure, or a configuration issue. To resolve this, you can try the following: 1) Check the cluster health and ensure all nodes are connected and working properly. 2) Verify the shard allocation settings and adjust if necessary. 3) If a node has failed, replace it or redistribute the shards. 4) If the issue persists, consider increasing the number of primary shards.

This guide will help you check for common problems that cause the log ” no primary shards available for shard [” + shard + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, shards, plugin.

Log Context

Log ” no primary shards available for shard [” + shard + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  String nodeId = shard.currentNodeId();
 nodesAndShards.computeIfAbsent(nodeId; k -> new HashSet<>()).add(shard.shardId());
 } else {
 throw new NoShardAvailableActionException(shard.shardId(); " no primary shards available for shard [" + shard + "]");
 return nodesAndShards;


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?