Cannot run cleanup on readonly repository – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.4-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 you try to perform a cleanup operation on a repository that is set to read-only mode in Elasticsearch. This mode prevents any write operations, including cleanup. To resolve this issue, you can either change the repository settings to read-write mode or create a new repository with write permissions. Additionally, ensure that the user executing the cleanup operation has the necessary permissions to perform write operations.

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 ” cannot run cleanup on readonly repository ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repository, repositories.

Log Context

Log “cannot run cleanup on readonly repository” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * @param listener              Listener to complete when done
 public void cleanup(long repositoryStateId; Version repositoryMetaVersion; ActionListener listener) {
 try {
 if (isReadOnly()) {
 throw new RepositoryException(; "cannot run cleanup on readonly repository");
 Map rootBlobs = blobContainer().listBlobs();
 final RepositoryData repositoryData = safeRepositoryData(repositoryStateId; rootBlobs);
 final Map foundIndices = blobStore().blobContainer(indicesPath()).children();
 final Set survivingIndexIds = repositoryData.getIndices()


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