Snapshot retention deleting snapshot – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-8.9

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 Elasticsearch tries to delete an old snapshot due to retention policy but fails. This could be due to insufficient permissions, a locked file, or a network issue. To resolve this, ensure that Elasticsearch has the necessary permissions to delete snapshots. If a file is locked, unlock it or restart the Elasticsearch service. If it’s a network issue, check the connection to the snapshot repository. Also, verify the snapshot retention policy to ensure it’s correctly configured.

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 ” [{}] snapshot retention deleting snapshot [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, snapshot.

Log Context

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

        String repo;
        SnapshotId snapshot;
        SnapshotLifecycleStats slmStats;
        ActionListener listener
    ) {
        logger.info("[{}] snapshot retention deleting snapshot [{}]"; repo; snapshot);
        // don't time out on this request to not produce failed SLM runs in case of a temporarily slow master node
        client.admin()
            .cluster()
            .prepareDeleteSnapshot(repo; snapshot.getName())
            .setMasterNodeTimeout(TimeValue.MAX_VALUE)

 

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?