Corrupt file detected source but is set to – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Corrupt file detected source but is set to ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file and index.

Log Context

Log “corrupt file detected source: [{}] but [{}] is set to [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (Lucene.isCorruptionException(t)) {
            if (engineConfig.isFailEngineOnCorruption()) {
                failEngine("corrupt file (source: [" + source + "])"; t);
                return true;
            } else {
                logger.warn("corrupt file detected source: [{}] but [{}] is set to [{}]"; t; source;
                        EngineConfig.INDEX_FAIL_ON_CORRUPTION_SETTING; engineConfig.isFailEngineOnCorruption());
        } else if (ExceptionsHelper.isOOM(t)) {
            failEngine("out of memory (source: [" + source + "])"; t);
            return true;


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?

Analyze your cluster & get personalized recommendations

Skip to content