Transform finished indexing all data initiating stop – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-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 an Elasticsearch transform job has completed indexing all the data and is initiating a stop. This is not necessarily an error, but more of an informational message indicating the end of a process. If you didn’t expect the job to stop, check the job configuration and the data source. Ensure the job is set to continuous if you want it to keep running. Also, verify that your data source is continuously receiving new data. If the job is stopping prematurely, check for underlying issues like resource constraints or network interruptions.

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 finished indexing all data; initiating stop. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, indexing.

Log Context

Log “[{}] transform finished indexing all data; initiating stop.” classname is TransformIndexer.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (indexerState.equals(IndexerState.STARTED) && context.getCheckpoint() == 1 && this.isContinuous() == false) {
            // set both to stopped so they are persisted as such
            indexerState = IndexerState.STOPPED;

            auditor.info(transformConfig.getId(); "Transform finished indexing all data; initiating stop");
            logger.info("[{}] transform finished indexing all data; initiating stop."; transformConfig.getId());
        }

        // If we are `STOPPED` on a `doSaveState` call; that indicates we transitioned to `STOPPED` from `STOPPING`
        // OR we called `doSaveState` manually as the indexer was not actively running.
        // Since we save the state to an index; we should make sure that our task state is in parity with the indexer state

 

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?