Cannot delete test data at – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-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 Elasticsearch is unable to delete specific data, possibly due to insufficient permissions, incorrect index name, or the data is currently in use. To resolve this, ensure you have the correct permissions to delete data. Check if the index name is correct and the data is not being used by any ongoing processes. If the data is locked, try unlocking or closing the index before deletion. Also, ensure the Elasticsearch cluster is in a healthy state.

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 delete test data at ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: blobstore, delete, repositories.

Log Context

Log “cannot delete test data at” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (isReadOnly() == false) {
 try {
 final String testPrefix = testBlobPrefix(seed);
 } catch (Exception exp) {
 throw new RepositoryVerificationException(; "cannot delete test data at " + basePath(); exp);
 }  // Tracks the latest known repository generation in a best-effort way to detect inconsistent listing of root level index-N blobs


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?