Log Remote file corruption on node ; recovering . local checksum OK – How To Solve Related Issues


Log Remote file corruption on node ; recovering . local checksum OK – How To Solve Related Issues

Opster Team

Jan-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 ” Remote file corruption on node ; recovering . 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, handler, indices, node and recovery.

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

                 throw corruptIndexException;
            } else { // corruption has happened on the way to replica
                RemoteTransportException exception = new RemoteTransportException(
                    "File corruption occurred on recovery but checksums are ok"; null);
                exception.addSuppressed(e);
                logger.warn(() -> new ParameterizedMessage("{} Remote file corruption on node {}; recovering {}. local checksum OK";
                    shardId; request.targetNode(); md); corruptIndexException);
                throw exception;
            }
        } else {
            throw e;




 

Optimize Elasticsearch Performance

Try The Tool