Snapshot with the same name is already 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.

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

Log Context

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

}; "create_snapshot [" + snapshotName + ']'; listener::onFailure);
 private static void ensureSnapshotNameNotRunning(SnapshotsInProgress runningSnapshots; String repositoryName; String snapshotName) {
 if (runningSnapshots.forRepo(repositoryName).stream().anyMatch(s -> s.snapshot().getSnapshotId().getName().equals(snapshotName))) {
 throw new InvalidSnapshotNameException(repositoryName; snapshotName; "snapshot with the same name is already in-progress");
 // TODO: It is worth revisiting the design choice of creating a placeholder entry in snapshots-in-progress here once we have a cache
 // for repository metadata and loading it has predictable performance


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content