Error while reading global checkpoint from translog – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch encounters an issue while trying to read the global checkpoint from the transaction log (translog). This could be due to corruption in the translog, disk I/O issues, or a bug in Elasticsearch. To resolve this, you can try to recover the translog, check the health of your disk, or upgrade Elasticsearch to the latest version. If the issue persists, you may need to reindex your data. Always ensure to have a backup of your data to prevent data loss.

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: recovery, indices.

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 :

            try {
                final String expectedTranslogUUID = metadataSnapshot.getCommitUserData().get(Translog.TRANSLOG_UUID_KEY);
                final long globalCheckpoint = Translog.readGlobalCheckpoint(recoveryTarget.translogLocation(); expectedTranslogUUID);
                assert globalCheckpoint + 1 >= startingSeqNo : "invalid startingSeqNo " + startingSeqNo + " >= " + globalCheckpoint;
            } 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;
                startingSeqNo = UNASSIGNED_SEQ_NO;
        } catch (final org.apache.lucene.index.IndexNotFoundException e) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?