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 analyzes 2 JSON files to detect many configuration errors.

Briefly, this error suggests that the snapshot feature is not allowed or not enabled in the Elasticsearch cluster. In Elasticsearch, snapshots can be used to back up and restore data, but the feature needs to be enabled in the cluster settings. To resolve this error, check the Elasticsearch cluster settings and ensure that the snapshot feature is enabled. You may also need to configure the snapshot repository and the snapshot schedule.

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.

Take a self-guided product tour to see for yourself (no registration required).

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

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.


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content