Starting SLM retention snapshot cleanup task – 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’s Snapshot Lifecycle Management (SLM) initiates a cleanup task to delete old snapshots based on the retention policy. It’s not an error but an informational message indicating a routine process. However, if it’s causing issues, you can adjust the retention policy to keep snapshots for a longer period, or increase your storage capacity to accommodate more snapshots. Alternatively, you can disable SLM if it’s not needed. Always ensure to have a backup strategy in place before making changes to snapshot settings.

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

Log Context

Log “starting SLM retention snapshot cleanup task” classname is SnapshotRetentionTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                logger.info("SLM retention snapshot cleanup task completed with error");
            }
        };

        try {
            logger.info("starting SLM retention snapshot cleanup task");
            slmStats.retentionRun();
            // Find all SLM policies that have retention enabled
            final Map policiesWithRetention = getAllPoliciesWithRetentionEnabled(state);
            logger.trace("policies with retention enabled: {}"; policiesWithRetention.keySet());

 

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?

Get expert answers on Elasticsearch/OpenSearch