Failed to delete snapshot – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

Briefly, this error occurs when Elasticsearch is unable to delete a snapshot, which can be due to a variety of issues, such as a missing snapshot or an issue with the snapshot repository. To resolve this issue, you can try to check the snapshot repository and the snapshot itself for errors, or try to delete the snapshot again.

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. Take a self-guided product tour to see for yourself (no registration required).

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

Log Context

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

                             logger.debug("deleted snapshot completed - deleting files");
                            threadPool.executor(ThreadPool.Names.SNAPSHOT).execute(() -> {
                                    try {
                                        deleteSnapshot(snapshot.getRepository(); snapshot.getSnapshotId().getName(); listener; true);
                                    } catch (Exception ex) {
                                        logger.warn(() -> new ParameterizedMessage("[{}] failed to delete snapshot"; snapshot); ex);
                        e -> {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content