Close request for job while it was vacating the node – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.15-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when an Elasticsearch job is being closed while it is also being moved from one node to another. This could be due to a node failure or a manual relocation of shards. To resolve this issue, you can try to manually relocate the job to a stable node before closing it. Alternatively, ensure that the node is stable and not under heavy load before closing the job. If the problem persists, consider increasing the timeout settings for job closing operations.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” [{}] Close request for job while it was vacating the node ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task, node, request.

Log Context

Log “[{}] Close request for job while it was vacating the node” classname is JobTask.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // If a job is vacating the node when a close request arrives; convert that vacate to a close.
        // This may be too late; if the vacate operation has already gone past the point of unassigning
        // the persistent task instead of completing it. But in general a close should take precedence
        // over a vacate.
        if (closingOrVacating.getAndSet(ClosingOrVacating.CLOSING) == ClosingOrVacating.VACATING) {
            logger.info("[{}] Close request for job while it was vacating the node"; jobId);
        }
        autodetectProcessManager.closeJob(this; reason);
    }

    public void killJob(String reason) {

 

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?