Node not connected – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to establish a connection with a specific node in the cluster. This could be due to network issues, incorrect configuration, or the node being down. To resolve this issue, you can check the network connectivity between nodes, verify the node’s configuration settings, or ensure the node is running and not overloaded. Additionally, checking the Elasticsearch logs can provide more detailed information about the cause of the error.

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

Log Context

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

 public Transport.Connection getConnection(DiscoveryNode node) {
 Transport.Connection connection = connectedNodes.get(node);
 if (connection == null) {
 throw new NodeNotConnectedException(node; "Node not connected");
 return connection;
 }  /**


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?