Datafeed for job was already stopped – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when you attempt to stop a datafeed in Elasticsearch that has already been stopped. This could be due to a manual stop command, a system error, or a scheduled stop. To resolve this issue, you can check the status of the datafeed to confirm if it’s already stopped. If it’s running, try stopping it again. If the error persists, check for system errors or network issues that might be causing the problem. Also, ensure that the job associated with the datafeed is running properly.

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

Log Context

Log “[{}] datafeed [{}] for job [{}] was already stopped” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    if (acquired) {
            } else {
      "[{}] datafeed [{}] for job [{}] was already stopped"; source; datafeedId; datafeedJob.getJobId());

         * This stops a datafeed WITHOUT updating the corresponding persistent task.  When called it


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?