Cannot close all jobs – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to close all running jobs, possibly due to some jobs being in a failed state or due to a lack of resources. To resolve this issue, you can try to manually close each job using the Close Job API. If a job is stuck, you may need to force close it. Also, ensure that your cluster has sufficient resources to handle all running jobs. If necessary, consider scaling up your cluster or reducing the number of concurrent jobs.

This guide will help you check for common problems that cause the log ” cannot close all jobs ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “cannot close all jobs” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        if (MachineLearningField.ML_API_FEATURE.checkWithoutTracking(licenseState) == false) {
            // if the license has expired; close jobs and datafeeds
            threadPool.generic().execute(new AbstractRunnable() {
                public void onFailure(Exception e) {
                    logger.warn("cannot close all jobs"; e);

                protected void doRun() throws Exception {
                    datafeedRunner.stopAllDatafeedsOnThisNode("invalid license");