Log Corrupt file detected source merge but is set to – How To Solve Related Issues


Log Corrupt file detected source merge 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 try running the 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 ” Corrupt file detected source merge but is set to ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: discovery-file and index.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log context

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

         public void onFailedMerge(MergePolicy.MergeException e) {
            if (Lucene.isCorruptionException(e)) {
                if (engineConfig.isFailEngineOnCorruption()) {
                    failEngine("corrupt file detected source: [merge]"; e);
                } else {
                    logger.warn("corrupt file detected source: [merge] but [{}] is set to [{}]"; e; EngineConfig.INDEX_FAIL_ON_CORRUPTION_SETTING; engineConfig.isFailEngineOnCorruption());
                }
            } else if (engineConfig.isFailOnMergeFailure()) {
                failEngine("merge exception"; e);
            }
        }




 

Optimize Elasticsearch Performance

Try The Tool