Closing job ; because – 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 ” Closing job ; because ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

             }

            if (reason == null) {
                logger.info("Closing job [{}]"; jobId);
            } else {
                logger.info("Closing job [{}]; because [{}]"; jobId; reason);
            }

            AutodetectCommunicator communicator = processContext.getAutodetectCommunicator();
            if (communicator == null) {
                logger.debug("Job [{}] is being closed before its process is started"; jobId);




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content