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 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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Ignoring recovery of a corrupt translog entry ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, recovery and shard.

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


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content