Unexpected datafeed failure for job jobId stopping – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch’s machine learning feature encounters an issue with a datafeed tied to a specific job, causing the job to stop. This could be due to various reasons such as network issues, insufficient permissions, or data inconsistencies. To resolve this, you can check the job’s configuration for any errors, ensure the datafeed is correctly set up, verify network connectivity, and confirm that the user has the necessary permissions. Additionally, checking the Elasticsearch logs may provide more detailed information about the cause of the error.

This guide will help you check for common problems that cause the log ” Unexpected datafeed failure for job [” + jobId + “] stopping… ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Unexpected datafeed failure for job [” + jobId + “] stopping…” classname is DatafeedRunner.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            logger.debug("Waiting [{}] before executing next realtime import for job [{}]"; delay; jobId);
            holder.cancellable = threadPool.schedule(new AbstractRunnable() {

                public void onFailure(Exception e) {
                    logger.error("Unexpected datafeed failure for job [" + jobId + "] stopping..."; e);
                    holder.stop("general_realtime_error"; TimeValue.timeValueSeconds(20); e);

                protected void doRun() {


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?