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

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

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: repositories, repository and blobstore.

Log Context

Log “cannot run cleanup on readonly repository”classname  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 =


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content