Job jobTask isVacating Vacating Closing – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.15-8.9

Briefly, this error occurs when a task in Elasticsearch, specifically a job task, is in the process of being vacated or closed. This could be due to a node shutdown or a manual task cancellation. To resolve this issue, you can either wait for the task to complete its vacating process or manually intervene. Manual intervention could involve identifying the task using the task management API and then cancelling it. Alternatively, if the task is part of a larger job, you may need to stop the job before the task can be vacated.

This guide will help you check for common problems that cause the log ” {} job [{}]”; 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.

Log Context

Log “{} job [{}]”; jobTask.isVacating() ? “Vacating” : “Closing” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            // its context will already have been removed from this map
            jobKilled = (processByAllocation.containsKey(allocationId) == false);
            if (jobKilled) {
                logger.debug("[{}] Cleaning up job opened after kill"; jobId);
            } else if (reason == null) {
      "{} job [{}]"; jobTask.isVacating() ? "Vacating" : "Closing"; jobId);
            } else {
      "{} job [{}]; because [{}]"; jobTask.isVacating() ? "Vacating" : "Closing"; jobId; reason);

            AutodetectCommunicator communicator = processContext.getAutodetectCommunicator();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?