Snapshot is not allowed – How to solve this Elasticsearch error

Snapshot is not allowed – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” snapshot is not allowed ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: shard, snapshot and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

final IndexShardState state = this.state; // one time volatile read
  // we allow snapshot on closed index shard; since we want to do one after we close the shard and before we close the engine
  if (state == IndexShardState.STARTED || state == IndexShardState.CLOSED) {
  return getEngine().acquireLastIndexCommit(flushFirst);
  } else {
  throw new IllegalIndexShardStateException(shardId; state; "snapshot is not allowed");
  * Snapshots the most recent safe index commit from the currently running engine.

Run the Check-Up to get customized recommendations like this:


Heavy merges detected in specific nodes



A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…


Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…


X-PUT curl -H [a customized recommendation]


Optimize Elasticsearch Performance

Try The Tool