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 OpenSearch operation.
Briefly, this error occurs when OpenSearch is unable to mark a data store as corrupted due to insufficient permissions or a locked file. This could be due to the OpenSearch process not having the necessary permissions to modify the store files, or another process may be using the files, preventing OpenSearch from accessing them. To resolve this issue, ensure that the OpenSearch process has the correct permissions to modify the store files. If the files are locked by another process, identify and stop that process. Alternatively, you may need to restart the OpenSearch service.
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 ” store cannot be marked as corrupted ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: repositories, blobstore.
Log Context
Log “store cannot be marked as corrupted” classname is BlobStoreRepository.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
success = true;
} catch (CorruptIndexException | IndexFormatTooOldException | IndexFormatTooNewException ex) {
try {
store.markStoreCorrupted(ex);
} catch (IOException e) {
logger.warn("store cannot be marked as corrupted"; e);
}
throw ex;
} finally {
if (success == false) {
store.deleteQuiet(fileInfo.physicalName());
