Failure occurred while shutting down node – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.9-8.9

Briefly, this error occurs when there is an issue in the process of shutting down an Elasticsearch node. This could be due to various reasons such as a network disruption, a process interruption, or a resource constraint. To resolve this issue, you can try the following: 1) Check the node’s logs for more detailed error information. 2) Ensure that there are no ongoing operations that might be disrupted by the shutdown. 3) Check the system’s resources to ensure there’s enough memory and CPU. 4) If the problem persists, consider restarting the node or the entire cluster.

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

Log Context

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

 throw new IllegalStateException(
 "Node didn't stop within 10 seconds. " + "Any outstanding requests or tasks might get killed."
 } catch (IOException ex) {
 throw new ElasticsearchException("Failure occurred while shutting down node"; ex);
 } catch (InterruptedException e) {
 LogManager.getLogger(Elasticsearch.class).warn("Thread got interrupted while waiting for the node to shutdown.");
 } finally {
 LoggerContext context = (LoggerContext) LogManager.getContext(false);


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?