There are no repositories to fetch SLM retention snapshot cleanup task complete – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-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) tries to clean up old snapshots but doesn’t find any repositories to fetch. This could be due to misconfiguration or deletion of repositories. To resolve this issue, you can either create a new repository or reconfigure the existing one. Also, ensure that the SLM policy is correctly set to point to the existing repository. Lastly, check the Elasticsearch logs for any related errors that might help in troubleshooting.

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

Log Context

Log “there are no repositories to fetch; SLM retention snapshot cleanup task complete” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            logger.trace("fetching snapshots from repositories: {}"; repositioriesToFetch);

            if (repositioriesToFetch.isEmpty()) {
      "there are no repositories to fetch; SLM retention snapshot cleanup task complete");
            // Finally; asynchronously retrieve all the snapshots; deleting them serially;
            // before updating the cluster state with the new metrics and setting 'running'
            // back to false


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?