Failed to close node on failed start – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch encounters an issue while starting up and fails to close the node properly. This could be due to insufficient system resources, incorrect configuration settings, or a corrupted index. To resolve this issue, you can try increasing system resources, checking and correcting your configuration settings, or repairing or deleting the corrupted index. Additionally, ensure that Elasticsearch has the necessary permissions to access its data directories.

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

Log Context

Log “failed to close node {} on failed start” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                for (Node otherNode : nodes) {
                    try {
                    } catch (Exception inner) {
                        logger.warn((Supplier>) () -> new ParameterizedMessage("failed to close node {} on failed start"; otherNode); inner);
                throw ExceptionsHelper.convertToRuntime(e);


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?