How To Solve Issues Related to Log – Cannot close all jobs

How To Solve Issues Related to Log – Cannot close all jobs

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 “Cannot close all jobs” it’s important to understand a few problems related to Elasticsearch concepts license, plugin. See bellow important tips and explanations on these concepts

Log Context

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

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

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


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 How to stop

91.96 K 75

Github Issue Number 31794  

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