Log Successfully set job state to for job – How To Solve Related Issues


Log Successfully set job state to for job – 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 that cause many errors.

This guide will help you check for common problems that cause the log ” Successfully set job state to for job ” 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

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

     void setJobState(JobTask jobTask; JobState state) {
        JobTaskState jobTaskState = new JobTaskState(state; jobTask.getAllocationId());
        jobTask.updatePersistentTaskState(jobTaskState; new ActionListener>() {
            
Override
            public void onResponse(PersistentTask> persistentTask) {
                logger.info("Successfully set job state to [{}] for job [{}]"; state; jobTask.getJobId());
            }

            
Override
            public void onFailure(Exception e) {
                logger.error("Could not set job state to [" + state + "] for job [" + jobTask.getJobId() + "]"; e);


 

Optimize Elasticsearch Performance

Try The Tool