Failed to stop node – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.8

Briefly, this error occurs when Elasticsearch encounters an issue while trying to stop a node. This could be due to a variety of reasons such as insufficient permissions, a network issue, or a problem with the node itself. To resolve this issue, you could try restarting the Elasticsearch service, checking the node’s health and logs for any anomalies, ensuring the user has the necessary permissions, or checking the network connectivity. If the problem persists, you may need to consider reindexing or even rebuilding the node.

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

Log Context

Log “failed to stop 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("failed to stop 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?