Starting snapshot retention deletion for snapshots – How to solve related issues

Opster Team

Feb-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.

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 ” Starting snapshot retention deletion for snapshots ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, snapshot and task.

Log Context

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

     void deleteSnapshots(Map> snapshotsToDelete;
                         TimeValue maximumTime;
                         SnapshotLifecycleStats slmStats) {
        int count = snapshotsToDelete.values().stream().mapToInt(List::size).sum();"starting snapshot retention deletion for [{}] snapshots"; count);
        long startTime = nowNanoSupplier.getAsLong();
        final AtomicInteger deleted =  new AtomicInteger(0);
        final AtomicInteger failed = new AtomicInteger(0);
        for (Map.Entry> entry : snapshotsToDelete.entrySet()) {
            String repo = entry.getKey();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content