Read not allowed on IndexShard – 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.

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 ” Read not allowed on IndexShard ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard, index.

Log Context

Log “Read not allowed on IndexShard”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (readAllowed) {
 refreshListeners.addOrNotify(checkpoint; listener);
 } else {
 // we're not yet ready for reads; fail to notify client
 listener.onFailure(new IllegalIndexShardStateException(shardId; state; "Read not allowed on IndexShard"));
 private static class RefreshMetricUpdater implements ReferenceManager.RefreshListener {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content