Missing shard – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

Briefly, this error occurs when Elasticsearch cannot find the specified shard. The solution is to check the shard name or ID and ensure that it exists and is spelled correctly.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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

Log Context

Log “missing shard”classname  is TransportRollupIndexerAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

ClusterState clusterState
 ) {
 for (int i = 0; i < shardsResponses.length(); i++) {
 Object shardResponse = shardsResponses.get(i);
 if (shardResponse == null) {
 throw new ElasticsearchException("missing shard");
 } else if (shardResponse instanceof Exception) {
 throw new ElasticsearchException((Exception) shardResponse);
 return new RollupIndexerAction.Response(true);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content