Failed to put shutdown for node request getNodeId – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8.3-8.9

Briefly, this error occurs when Elasticsearch fails to execute a shutdown request for a specific node, identified by its node ID. This could be due to network issues, node unavailability, or insufficient permissions. To resolve this, you can try the following: 1) Check the network connectivity between the nodes; 2) Ensure the node is up and running; 3) Verify that the user executing the shutdown command has the necessary permissions; 4) Check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” failed to put shutdown for node [” + request.getNodeId() + “] ” 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 “failed to put shutdown for node [” + request.getNodeId() + “]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

    // package private for tests
    record PutShutdownNodeTask(Request request; ActionListener listener) implements ClusterStateTaskListener {
        public void onFailure(Exception e) {
            logger.error(() -> "failed to put shutdown for node [" + request.getNodeId() + "]"; e);

    // package private for tests


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?