File corruption on recovery local checksum OK – How to solve related issues

File corruption on recovery local checksum OK – 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 ” File corruption on recovery local checksum OK ” 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, indices, recovery and source.

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 “{} File corruption on recovery {} local checksum OK” classname is RecoverySource.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
                                        } else { // corruption has happened on the way to replica
                                            RemoteTransportException exception = new RemoteTransportException("File corruption occured on recovery but checksums are ok"; null);
                                            exception.addSuppressed(e);
                                            exceptions.add(0; exception); // last exception first
                                            logger.warn("{} File corruption on recovery {} local checksum OK"; corruptIndexException; shard.shardId(); md);
                                        }
                                    } else {
                                        exceptions.add(0; e); // last exceptions first
                                    }
                                } finally {




 

Run the Check-Up to get a customized report like this:

Analyze your cluster