Stopping datafeed for job ; acquired . – How to solve related issues

Stopping datafeed for job ; acquired . – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 ” Stopping datafeed for job ; acquired . ” 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 “[{}] stopping datafeed [{}] for job [{}]; acquired [{}]…” classname is DatafeedManager.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             datafeedJob.getJobId());
                    acquired = datafeedJobLock.tryLock(timeout.millis(); TimeUnit.MILLISECONDS);
                } catch (InterruptedException e1) {
                    Thread.currentThread().interrupt();
                } finally {
                    logger.info("[{}] stopping datafeed [{}] for job [{}]; acquired [{}]..."; source; datafeedId;
                            datafeedJob.getJobId(); acquired);
                    runningDatafeedsOnThisNode.remove(allocationId);
                    if (cancellable != null) {
                        cancellable.cancel();
                    }




 

Run the Check-Up to get a customized report like this:

Analyze your cluster