global checkpoint sync failed – 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.

Briefly, this error occurs when there is a failure in the process of syncing global checkpoint across all the nodes in the Elasticsearch cluster. A global checkpoint is a point in the Elasticsearch index where all operations up to that point have been flushed and acknowledged, and any failure in its sync process can lead to data loss or corruption. To resolve this issue, one can try restarting the affected node or cluster, or even restoring from a backup.

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 ” global checkpoint sync failed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “{} global checkpoint sync failed” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    new Request(shardId);
                    ActionListener.wrap(r -> {
                    }; e -> {
                        if (ExceptionsHelper.unwrap(e; AlreadyClosedException.class; IndexShardClosedException.class) == null) {
                   ParameterizedMessage("{} global checkpoint sync failed"; shardId); e);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content