GetJobId failed to persist transform state – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch fails to save the state of a data transformation job due to issues like insufficient permissions, disk space, or network connectivity. To resolve this, ensure that the Elasticsearch cluster has enough disk space and proper write permissions. Also, check the network connectivity between nodes. If the issue persists, consider increasing the timeout settings or reviewing the job configuration for potential errors.

This guide will help you check for common problems that cause the log ” [” + getJobId() + “] failed to persist transform state. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[” + getJobId() + “] failed to persist transform state.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    "Timed out (" + PERSIST_STOP_AT_CHECKPOINT_TIMEOUT_SEC + "s) waiting for transform state to be stored.";
        } catch (Exception e) {
            logger.error(() -> "[" + getJobId() + "] failed to persist transform state."; e);

    private boolean addSetStopAtCheckpointListener(boolean shouldStopAtCheckpoint; ActionListener shouldStopAtCheckpointListener)


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?