Attempt to stop datafeed for job – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when there’s an attempt to stop a datafeed for a job in Elasticsearch, but the datafeed is not found or is already stopped. This could be due to incorrect job ID or a timing issue. To resolve this, ensure the correct job ID is used. If the job ID is correct, check if the datafeed is already stopped. If it’s a timing issue, try to stop the datafeed again after some time. Also, ensure that the Elasticsearch cluster is healthy and functioning properly.

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

Log Context

Log “[{}] attempt to stop datafeed [{}] for job [{}]” classname is DatafeedRunner.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        public void stop(String source; TimeValue timeout; Exception e; boolean autoCloseJob; String stoppedReason) {
            if (isNodeShuttingDown) {
                return;
            }

            logger.info("[{}] attempt to stop datafeed [{}] for job [{}]"; source; datafeedId; datafeedJob.getJobId());
            if (datafeedJob.stop()) {
                boolean acquired = false;
                try {
                    logger.info(
                        "[{}] try lock [{}] to stop datafeed [{}] for job [{}]...";

 

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?