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

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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Datafeed is stopping because job state is ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

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




 

Run the Check-Up to get a customized report like this:

Analyze your cluster