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



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

Opster Team

Feb-20, Version: 1.7-8.0

 

Before you read this guide, we recommend you run the Elasticsearch Error Check-Up which detects issues in ES that cause log errors. It’s a free tool that requires no installation and takes 2 minutes to complete.

This guide will help you check for common problems that cause the log ” Corrupt file detected source 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. Among the dozens of checks included are: shards sizes, thread pools, management queue size, search errors, circuit breakers and many more (join over 700 users who use this free tool).

Log Context

Log “corrupt file detected source: [{}] but [{}] is set to [{}]” classname is Engine.java
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;






Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Github Issue Number 7238

2 Nested Corruptindexexception Failed






Optimize Elasticsearch Performance

Try The Tool