Briefly, this error occurs when Elasticsearch is unable to find or process a job with the given JobId. This could be due to the job not existing, the job being in a state that doesn’t allow the requested operation, or a network or server issue. To resolve this, ensure the JobId is correct and the job exists. Check the job’s state and make sure it’s in a state that allows the requested operation. If the problem persists, investigate for any network or server issues.
This guide will help you check for common problems that cause the log ” [” + jobId + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “[” + jobId + “] ” classname is AutodetectProcessManager.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
throw exception;
}
String msg = jobKilled
? "Exception cleaning up autodetect process started after kill"
: "Exception " + (jobTask.isVacating() ? "vacating" : "closing") + " autodetect process";
logger.warn("[" + jobId + "] " + msg; e);
setJobState(jobTask; JobState.FAILED; e.getMessage());
throw ExceptionsHelper.serverError(msg; e);
} finally {
// to ensure the contract that multiple simultaneous close calls for the same job wait until
// the job is closed is honoured; hold the lock throughout the close procedure so that another
