Couldnt marks store corrupted – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Couldnt marks store corrupted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

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 “Couldn’t marks store corrupted” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 // the shard is initializing
                if (Lucene.isCorruptionException(failure)) {
                    try {
                        store.markStoreCorrupted(ExceptionsHelper.unwrap(failure; CorruptIndexException.class));
                    } catch (IOException e) {
                        logger.warn("Couldn't marks store corrupted"; e);
            } finally {
                assert !readLock.assertLockIsHeld() : "readLock is held by a thread that tries to fail the engine";
                if (failedEngine != null) {


Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content