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

Opster Team

Aug-23, Version: 7.15-8.9

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.

Log Context

Log “{} job [{}]; because [{}]”; jobTask.isVacating() ? “Vacating” : “Closing” classname is
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) {
      "{} job [{}]"; jobTask.isVacating() ? "Vacating" : "Closing"; jobId);
            } else {
      "{} job [{}]; because [{}]"; jobTask.isVacating() ? "Vacating" : "Closing"; jobId; reason);

            AutodetectCommunicator communicator = processContext.getAutodetectCommunicator();
            if (communicator == null) {
                assert jobKilled == false


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?