Job jobId deleted – How to solve related issues

Average Read Time

2 Mins

Job jobId deleted – How to solve related issues

Opster Team

Dec-19, 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 ” Job jobId deleted ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: delete.

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 “Job jobId deleted” classname is TransportDeleteJobAction.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        // Step 4. When the job has been removed from the cluster state; return a response
        // -------
        CheckedConsumer apiResponseHandler = jobDeleted -> {
            if (jobDeleted) {
                logger.info("Job [" + jobId + "] deleted");
                auditor.info(jobId; Messages.getMessage(Messages.JOB_AUDIT_DELETED));
                listener.onResponse(new AcknowledgedResponse(true));
            } else {
                listener.onResponse(new AcknowledgedResponse(false));
            }

 

Run the Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content