Log Closing jobs; because – How To Solve Related Issues



Log Closing jobs; because – 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 causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Closing jobs; because” 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 discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”Closing [{}] jobs; because [{}]” classname is AutodetectProcessManager.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     }

    public synchronized void closeAllJobsOnThisNode(String reason) {
        int numJobs = processByAllocation.size();
        if (numJobs != 0) {
            logger.info("Closing [{}] jobs; because [{}]"; numJobs; reason);

            for (ProcessContext process : processByAllocation.values()) {
                closeJob(process.getJobTask(); false; reason);
            }
        }




 

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 Could Not Start Datafeed For Jobnam  

Github Issue Number 31794  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now