A snapshot is already running – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when an Elasticsearch snapshot operation is already in progress and another snapshot operation is initiated. Elasticsearch does not allow concurrent snapshot operations to prevent data inconsistency. To resolve this issue, you can either wait for the current snapshot operation to complete before initiating another one, or you can cancel the ongoing snapshot operation using the delete snapshot API, and then start the new snapshot operation. However, be cautious as cancelling a snapshot operation may lead to incomplete backups.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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

Log Context

Log “a snapshot is already running” class name is SnapshotsService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (snapshots != null
 && snapshots.asStream()
 entry -> (entry.state() == State.INIT && initializingSnapshots.contains(entry.snapshot()) == false) == false
 )) {
 throw new ConcurrentSnapshotExecutionException(repositoryName; snapshotName; " a snapshot is already running");
 // Store newSnapshot here to be processed in clusterStateProcessed
 indices = Arrays.asList(indexNameExpressionResolver.concreteIndexNames(currentState; request));  final List dataStreams = indexNameExpressionResolver.dataStreamNames(


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?