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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 =


Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content