Node closed while execution action for request – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 8-8.9

Briefly, this error occurs when an Elasticsearch node shuts down or becomes unresponsive during the execution of a request. This could be due to various reasons such as high load, network issues, or hardware failure. To resolve this issue, you can try the following: 1) Check the node’s logs for any signs of issues. 2) Monitor the node’s resource usage to ensure it’s not overloaded. 3) Check the network connectivity between the nodes. 4) If the node is consistently failing, consider replacing the hardware or increasing its resources.

This guide will help you check for common problems that cause the log ” node closed while execution action [{}] for request [{}] ” 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 closed while execution action [{}] for request [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                client.execute(action; request; listener);

            public void onClusterServiceClose() {
                logger.warn("node closed while execution action [{}] for request [{}]";; request);
                listener.onFailure(new NodeClosedException(clusterService.localNode()));

            public void onTimeout(TimeValue timeout) {


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?