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


Log Remote file corruption during finalization on node ; recovering . 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 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 during finalization 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: 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 during finalization 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 remoteException;
                                }
                                // corruption has happened on the way to replica
                                RemoteTransportException exception = new RemoteTransportException("File corruption occurred on recovery but checksums are ok"; null);
                                exception.addSuppressed(remoteException);
                                logger.warn("{} Remote file corruption during finalization on node {}; recovering {}. local checksum OK";
                                        corruptIndexException; shard.shardId(); request.targetNode());
                                throw exception;
                            } else {
                                throw remoteException;
                            }




 

Optimize Elasticsearch Performance

Try The Tool