Failed to create checkpoint – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.4-8.2

Briefly, this error occurs when Elasticsearch is unable to create a checkpoint due to issues like insufficient disk space, incorrect file permissions, or network connectivity problems. To resolve this, you can free up disk space, check and correct file permissions, or troubleshoot network issues. Additionally, ensure that the Elasticsearch process has the necessary permissions to write to the checkpoint directory.

This guide will help you check for common problems that cause the log ” [{}] failed to create checkpoint. ” 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 create checkpoint.” classname is TransformIndexer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            getLastCheckpoint();
            ActionListener.wrap(
                checkpoint -> transformsConfigManager.putTransformCheckpoint(
                    checkpoint;
                    ActionListener.wrap(putCheckPointResponse -> listener.onResponse(checkpoint); createCheckpointException -> {
                        logger.warn(new ParameterizedMessage("[{}] failed to create checkpoint."; getJobId()); createCheckpointException);
                        listener.onFailure(
                            new RuntimeException(
                                "Failed to create checkpoint due to: " + createCheckpointException.getMessage();
                                createCheckpointException
                            )

 

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?