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 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 ” File corruption on recovery local checksum OK ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-file, indices, recovery and source.

Log Context

Log “{} File corruption on recovery {} local checksum OK” classname is
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);
                                            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 {


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