Unexpectedly deleting path from a readonly repository – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.2

Briefly, this error occurs when Elasticsearch attempts to delete data from a repository that has been set to read-only. This could be due to incorrect permissions or a misconfiguration. To resolve this issue, you can either change the repository’s permissions to allow write operations or ensure that no delete operations are being attempted on the read-only repository. Additionally, check your Elasticsearch configuration to ensure it’s not mistakenly set to treat the repository as read-only.

This guide will help you check for common problems that cause the log ” unexpectedly deleting [” + path + “] from a readonly repository ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, repository.

Log Context

Log “unexpectedly deleting [” + path + “] from a readonly repository” class name is FsBlobStore.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public void delete(BlobPath path) throws IOException {
 assert readOnly == false : "should not delete anything from a readonly repository: " + path;
 //noinspection ConstantConditions in case assertions are disabled
 if (readOnly) {
 throw new ElasticsearchException("unexpectedly deleting [" + path + "] from a readonly repository");
 }  @Override