Snapshot is in progress – 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 a snapshot operation is already in progress in Elasticsearch. Elasticsearch can only perform one snapshot operation at a time, and this error is returned when a new snapshot is attempted while one is already in progress. To resolve the issue, wait for the current snapshot operation to complete before attempting a new one.

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 ” snapshot is in progress ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: repositories, snapshot.

Log Context

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

 private static void ensureRepositoryNotInUse(ClusterState clusterState; String repository) {
 final SnapshotsInProgress snapshots = clusterState.custom(SnapshotsInProgress.TYPE; SnapshotsInProgress.EMPTY);
 if (snapshots.forRepo(repository).isEmpty() == false) {
 throw newRepositoryConflictException(repository; "snapshot is in progress");
 for (SnapshotDeletionsInProgress.Entry entry : clusterState.custom(
 ).getEntries()) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content