Aborting as datafeed has been stopped – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-8.9

Briefly, this error occurs when a datafeed in Elasticsearch, used for machine learning jobs, is manually stopped or encounters an issue that forces it to stop. This could be due to a variety of reasons such as network issues, insufficient resources, or configuration errors. To resolve this, you can restart the datafeed, ensure that there are sufficient resources, and check the datafeed’s configuration for any errors. Additionally, check the Elasticsearch logs for any specific issues that might have caused the datafeed to stop.

This guide will help you check for common problems that cause the log ” [{}] Aborting as datafeed has been stopped ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “[{}] Aborting as datafeed has been stopped” classname is DatafeedRunner.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    public void onFailure(Exception e) {
                        if (ExceptionsHelper.unwrapCause(e) instanceof ResourceNotFoundException) {
                            // The task was stopped in the meantime; no need to do anything
                            logger.info("[{}] Aborting as datafeed has been stopped"; task.getDatafeedId());
                        } else {


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?