How To Solve Issues Related to Log – Datafeed for job was already stopped

How To Solve Issues Related to Log – Datafeed for job was already stopped

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Datafeed for job was already stopped” it’s important to understand a few problems related to Elasticsearch concepts plugin. See bellow important tips and explanations on these concepts

Log Context

Log”[{}] datafeed [{}] for job [{}] was already stopped” classname is DatafeedManager.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     if (acquired) {
                        datafeedJobLock.unlock();
                    }
                }
            } else {
                logger.info("[{}] datafeed [{}] for job [{}] was already stopped"; source; datafeedId; datafeedJob.getJobId());
            }
        }

        /**
         * This stops a datafeed WITHOUT updating the corresponding persistent task.  When called it




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Datafeed Stops Immediately When Per  

Could Not Start Datafeed For Jobnam  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now