Log Ignoring recovery of a corrupt translog entry – How To Solve Related Issues


Log Ignoring recovery of a corrupt translog entry – 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 ” Ignoring recovery of a corrupt translog entry ” 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: index, recovery and shard.

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 “Ignoring recovery of a corrupt translog entry” classname is IndexShard.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 opsRecovered++;
                onOperationRecovered.run();
            } catch (Exception e) {
                if (ExceptionsHelper.status(e) == RestStatus.BAD_REQUEST) {
                    // mainly for MapperParsingException and Failure to detect xcontent
                    logger.info("ignoring recovery of a corrupt translog entry"; e);
                } else {
                    throw ExceptionsHelper.convertToRuntime(e);
                }
            }
        }




 

Optimize Elasticsearch Performance

Try The Tool