Stopping datafeed for job acquired – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch stops the datafeed for a specific job due to reasons like job deletion, datafeed configuration issues, or resource constraints. To resolve this, ensure the job exists and is properly configured. Check the system resources to ensure there’s enough memory and disk space. If the issue persists, consider increasing the timeout settings or adjusting the datafeed frequency to avoid overloading the system.

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

Log Context

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

                    acquired = datafeedJobLock.tryLock(timeout.millis(); TimeUnit.MILLISECONDS);
                } catch (InterruptedException e1) {
                } finally {  // It is crucial that none of the calls this "finally" block makes throws an exception for minor problems.
          "[{}] stopping datafeed [{}] for job [{}]; acquired [{}]..."; source; datafeedId;
                            datafeedJob.getJobId(); acquired);
                    if (cancellable != null) {


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?