Failed to run repository cleanup operations on – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-7.5

Briefly, this error occurs when Elasticsearch is unable to perform cleanup operations on a repository due to issues like insufficient permissions, network connectivity problems, or the repository being in use by another process. To resolve this, you can check and adjust the permissions of the repository, ensure the network connection is stable, or stop any processes that may be using the repository. Additionally, check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” Failed to run repository cleanup operations on [{}][{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, repositories, repository, cluster.

Log Context

Log “Failed to run repository cleanup operations on [{}][{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                                if (failure == null) {
                          "Done with repository cleanup on [{}][{}] with result [{}]";
                                        repositoryName; repositoryStateId; result);
                                } else {
                                    logger.warn(() -> new ParameterizedMessage("Failed to run repository cleanup operations on [{}][{}]";
                                        repositoryName; repositoryStateId); failure);


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?