Datafeed for job has been stopped – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when the data feed for a specific job in Elasticsearch is halted. This could be due to various reasons such as network issues, insufficient resources, or configuration errors. To resolve this, you can try restarting the data feed, checking the job’s configuration for any errors, or ensuring that the Elasticsearch cluster has sufficient resources. Additionally, check the Elasticsearch logs for any specific error messages that might indicate the root cause of the problem.

This guide will help you check for common problems that cause the log ” [{}] datafeed [{}] for job [{}] 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 “[{}] datafeed [{}] for job [{}] has been stopped{}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                            Messages.getMessage(isIsolated() ? Messages.JOB_AUDIT_DATAFEED_ISOLATED : Messages.JOB_AUDIT_DATAFEED_STOPPED));
          "[{}] datafeed [{}] for job [{}] has been stopped{}"; source; datafeedId; datafeedJob.getJobId();
                            acquired ? "" : "; but there may be pending tasks as the timeout [" + timeout.getStringRep() + "] expired");
                    if (autoCloseJob && isIsolated() == false) {
                    if (acquired) {