Error while reading global checkpoint from translog; – How to solve related issues

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Error while reading global checkpoint from translog; ” 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: indices and 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 “Error while reading global checkpoint from translog;” classname is PeerRecoveryTargetService.java.
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) {




 

Run the Check-Up to get a customized report like this:

Analyze your cluster