Node closed – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.8-8.9

Briefly, this error occurs when an Elasticsearch node is shut down or becomes unresponsive. This could be due to a variety of reasons such as network issues, hardware failure, or the node being manually closed. To resolve this issue, you can try restarting the node, checking the node’s hardware, or investigating the network connection. If the node was manually closed, you can reopen it. Additionally, ensure that your cluster has enough resources to handle the workload and consider adding more nodes if necessary.

This guide will help you check for common problems that cause the log ” node closed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, cluster.

Log Context

Log “node closed” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final var nextBatch = takeNextBatch();
 assert currentlyExecutingBatch == nextBatch;
 if (lifecycle.started()) {;
 } else {
 nextBatch.onRejection(new FailedToCommitClusterStateException("node closed"; getRejectionException()));


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?