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 causing many log errors (free and no installation required)


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, 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 discover the cause of many errors and provides suitable actionable recommendations. 

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 :

            } 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);


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Corrupt Data Overrun In Decompress  

Github Issue Number 18972  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now