Transform is no longer in the middle of a checkpoint initiating stop – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.6-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when you try to stop an Elasticsearch Transform that is not currently in the middle of a checkpoint. This could be due to the Transform having already completed its task or being in an idle state. To resolve this issue, you can either wait for the Transform to reach its next checkpoint before attempting to stop it, or you can force stop the Transform using the force parameter in the stop Transform API. Alternatively, you can check the Transform’s state using the get Transform stats API before attempting to stop it.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [{}] transform is no longer in the middle of a checkpoint; initiating stop. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] transform is no longer in the middle of a checkpoint; initiating stop.” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // In either case; we should stop so that we guarantee a consistent state and that there are no partially completed checkpoints
        if (shouldStopAtCheckpoint && initialRun() && indexerState.equals(IndexerState.STARTED)) {
            indexerState = IndexerState.STOPPED;
  ; "Transform is no longer in the middle of a checkpoint; initiating stop.");
  "[{}] transform is no longer in the middle of a checkpoint; initiating stop."; transformConfig.getId());

        // This means that the indexer was triggered to discover changes; found none; and exited early.
        // If the state is `STOPPED` this means that TransformTask#stop was called while we were checking for changes.
        // Allow the stop call path to continue


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?

Get expert answers on Elasticsearch/OpenSearch