Log Datafeed for job has been stopped – How To Solve Related Issues

Log Datafeed for job has been stopped – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0


Before you begin reading this guide, we recommend you try running the 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 for job has been stopped ” 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 [{}] for job [{}] has been stopped{}” classname is DatafeedManager.java
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));
                    logger.info("[{}] 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) {


Optimize Elasticsearch Performance

Try The Tool