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

Opster Team

Aug-23, Version: 7.14-8.2

Briefly, this error occurs when Elasticsearch is unable to execute the shutdown command for a specific node. This could be due to network issues, insufficient permissions, or the node being unresponsive. To resolve this issue, you can try the following: 1) Check the network connectivity between the nodes; 2) Ensure that the user executing the command has the necessary permissions; 3) Check the health of the node and restart it if necessary; 4) If the problem persists, consider reconfiguring the cluster or upgrading Elasticsearch to the latest version.

This guide will help you check for common problems that cause the log ” failed to put shutdown for node [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, plugin.

Log Context

Log “failed to put shutdown for node [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


            public void onFailure(Exception e) {
                logger.error(new ParameterizedMessage("failed to put shutdown for node [{}]"; request.getNodeId()); e);

            public void clusterStateProcessed(ClusterState oldState; ClusterState newState) {


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?