Failed to persist should stop at checkpoint update – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-7.9

Briefly, this error occurs when Elasticsearch is unable to update the checkpoint during a data persistence operation. This could be due to insufficient disk space, network issues, or a problem with the underlying storage system. To resolve this issue, you can try freeing up disk space, checking the network connection, or investigating the health of your storage system. Additionally, ensure that your Elasticsearch cluster has the correct permissions to write to the disk. If the problem persists, consider restarting your Elasticsearch nodes or even the entire cluster.

This guide will help you check for common problems that cause the log ” [{}] failed to persist should_stop_at_checkpoint update [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] failed to persist should_stop_at_checkpoint update [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            // We only want to update this internal value if it is persisted as such
            logger.debug("[{}] successfully persisted should_stop_at_checkpoint update [{}]"; getJobId(); shouldStopAtCheckpoint);
        }; statsExc -> {
            logger.warn("[{}] failed to persist should_stop_at_checkpoint update [{}]"; getJobId(); shouldStopAtCheckpoint);



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?