Briefly, this error occurs when Elasticsearch is trying to close a job but it’s currently vacating, meaning it’s in the process of being moved from one node to another. This could be due to a node leaving the cluster or a manual transfer. To resolve this issue, you can either wait for the vacating process to complete before closing the job, or manually stop the job before initiating the vacating process. Additionally, ensure that your cluster has enough resources to handle the job transfer and closing processes simultaneously.
This guide will help you check for common problems that cause the log ” {} job [{}]; because [{}]”; jobTask.isVacating() ? “Vacating” : “Closing ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task.
Overview
A task is an Elasticsearch operation, which can be any request performed on an Elasticsearch cluster, such as a delete by query request, a search request and so on. Elasticsearch provides a dedicated Task API for the task management which includes various actions, from retrieving the status of current running tasks to canceling any long running task.
Examples
Get all currently running tasks on all nodes of the cluster
Apart from other information, the response of the below request contains task IDs of all the tasks which can be used to get detailed information about the particular task in question.
GET _tasks
Get detailed information of a particular task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in below request
GET _tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759
Get all the current tasks running on particular nodes
GET _tasks?nodes=nodeId1,nodeId2
Cancel a task
Where clQFAL_VRrmnlRyPsu_p8A:1132678759 is the ID of the task in the below request
POST /_tasks/clQFAL_VRrmnlRyPsu_p8A:1132678759/_cancel?pretty
Notes
- The Task API will be most useful when you want to investigate the spike of resource utilization in the cluster or want to cancel an operation.
Log Context
Log “{} job [{}]; because [{}]”; jobTask.isVacating() ? “Vacating” : “Closing” classname is AutodetectProcessManager.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (jobKilled) {
logger.debug("[{}] Cleaning up job opened after kill"; jobId);
} else if (reason == null) {
logger.info("{} job [{}]"; jobTask.isVacating() ? "Vacating" : "Closing"; jobId);
} else {
logger.info("{} job [{}]; because [{}]"; jobTask.isVacating() ? "Vacating" : "Closing"; jobId; reason);
}
AutodetectCommunicator communicator = processContext.getAutodetectCommunicator();
if (communicator == null) {
assert jobKilled == false
[ratemypost]
