%s global checkpoint sync failed – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch struggles to synchronize global checkpoints across all replicas of a shard. This could be due to network issues, heavy indexing load, or insufficient resources. To resolve this, you can try reducing the indexing load, increasing the resources (like memory or CPU), or checking the network connectivity between nodes. Also, ensure that the cluster is properly configured and that there are no issues with the underlying hardware.

This guide will help you check for common problems that cause the log ” %s global checkpoint sync failed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, cluster.

Log Context

Log “%s global checkpoint sync failed” classname is IndicesClusterStateService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                new GlobalCheckpointSyncAction.Request(shardId);
                ActionListener.wrap(r -> {}; e -> {
                    if (ExceptionsHelper.unwrap(e; AlreadyClosedException.class; IndexShardClosedException.class) == null) {
                        logger.info(() -> format("%s global checkpoint sync failed"; shardId); 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?