Datafeed is stopping because job state is – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Datafeed is stopping because job state is ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Datafeed [{}] is stopping because job [{}] state is [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 if (jobState == JobState.OPENING || jobHasOpenAutodetectCommunicator(currentTasks; datafeedTask) == false) {
                } else if (jobState == JobState.OPENED) {
                } else {
                    logger.warn("Datafeed [{}] is stopping because job [{}] state is [{}]";
                            datafeedTask.getDatafeedId(); getJobId(datafeedTask); jobState);
                    datafeedTask.stop("job_never_opened"; TimeValue.timeValueSeconds(20));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content