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 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 ” Successfully set job state to for job ” 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 “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);


 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content