Failed to delete snapshot snapshotId – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.7

Briefly, this error occurs when Elasticsearch fails to delete a snapshot due to reasons like the snapshot is currently in use, the snapshot doesn’t exist, or there are insufficient permissions. To resolve this, ensure the snapshot isn’t being used by any restore operations. If it doesn’t exist, check the snapshot ID for any errors. Lastly, verify that the user has the necessary permissions to delete snapshots.

This guide will help you check for common problems that cause the log ” failed to delete snapshot [” + snapshotId + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: snapshot, blobstore, repositories, delete.

Log Context

Log “failed to delete snapshot [” + snapshotId + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // delete an index that was created by another master node after writing this index-N blob.
 final Map foundIndices = blobStore().blobContainer(indicesPath()).children();
 doDeleteShardSnapshots(snapshotId; repositoryStateId; foundIndices; rootBlobs; repositoryData;
 SnapshotsService.useShardGenerations(repositoryMetaVersion); listener);
 } catch (Exception ex) {
 listener.onFailure(new RepositoryException(; "failed to delete snapshot [" + snapshotId + "]"; ex));
 }  /**