Node request getNodeId is not currently shutting down – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.14-8.9

Briefly, this error occurs when an attempt is made to interact with a node that is not in the process of shutting down. This could be due to a miscommunication or a timing issue within the cluster. To resolve this issue, you can try the following: 1) Check the status of the node and ensure it’s operational. 2) If the node is stuck, try restarting it. 3) Ensure that the cluster state is healthy and all nodes are properly communicating. 4) Check your Elasticsearch logs for any underlying issues that may be causing this error.

This guide will help you check for common problems that cause the log ” node [” + request.getNodeId() + “] is not currently shutting down ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node, request.

Log Context

Log “node [” + request.getNodeId() + “] is not currently shutting down” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 protected void masterOperation(Task task; Request request; ClusterState state; ActionListener listener)
 throws Exception {
 { // This block solely to ensure this NodesShutdownMetadata isn't accidentally used in the cluster state update task below
 NodesShutdownMetadata nodesShutdownMetadata = state.metadata().custom(NodesShutdownMetadata.TYPE);
 if (nodesShutdownMetadata == null || nodesShutdownMetadata.get(request.getNodeId()) == null) {
 throw new ResourceNotFoundException("node [" + request.getNodeId() + "] is not currently shutting down");
 "delete-node-shutdown-" + request.getNodeId();
 new DeleteShutdownNodeTask(request; listener);


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?