Successfully aborted snapshot – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-7.17

Briefly, this error occurs when an ongoing snapshot operation in Elasticsearch is manually aborted by a user. This could be due to various reasons such as the snapshot taking too long, or the need to free up resources. To resolve this issue, you can either wait for the snapshot to complete before initiating the abort command, or increase the resources allocated to Elasticsearch to handle the snapshot operation more efficiently. Also, ensure that the snapshot repository is correctly configured and accessible to avoid any interruptions during the snapshot process.

This guide will help you check for common problems that cause the log ” Successfully aborted snapshot [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot.

Log Context

Log “Successfully aborted snapshot [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    deleteFromRepoTask.clusterStateProcessed(source; oldState; newState);
                if (abortedDuringInit) {
                    // BwC Path where we removed an outdated INIT state snapshot from the cluster state
          "Successfully aborted snapshot [{}]"; runningSnapshot);
                    if (outstandingDeletes.isEmpty()) {
                    } else {


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?