Error while reading global checkpoint from translog; – 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.

This guide will help you check for common problems that cause the log ” Error while reading global checkpoint from translog; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices and recovery.

Log Context

Log “Error while reading global checkpoint from translog;” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         long startingSeqNo = SequenceNumbers.UNASSIGNED_SEQ_NO;
        if (metadataSnapshot.size() > 0) {
            try {
                startingSeqNo = getStartingSeqNo(logger; recoveryTarget);
            } catch (IOException | TranslogCorruptedException e) {
                logger.warn(new ParameterizedMessage("error while reading global checkpoint from translog; " +
                    "resetting the starting sequence number from {} to unassigned and recovering as if there are none"; startingSeqNo); e);
                metadataSnapshot = Store.MetadataSnapshot.EMPTY;
        if (startingSeqNo == SequenceNumbers.UNASSIGNED_SEQ_NO) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content