Invalid DiscoveryNode server name configuredServerName – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when the Elasticsearch node’s name, specified in the configuration file, is invalid or not recognized. This could be due to a typo, incorrect formatting, or the node not existing. To resolve this issue, you can: 1) Check the node’s name in the configuration file for any typos or incorrect formatting. 2) Verify that the node exists and is properly connected to the cluster. 3) If the node is new, ensure it has been correctly added to the cluster. 4) Restart the Elasticsearch service after making any changes.

This guide will help you check for common problems that cause the log ” invalid DiscoveryNode server_name [” + configuredServerName + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, node, discovery.

Log Context

Log “invalid DiscoveryNode server_name [” + configuredServerName + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 String configuredServerName = node.getAttributes().get("server_name");
 if (configuredServerName != null) {
 try {
 serverName = new SNIHostName(configuredServerName);
 } catch (IllegalArgumentException e) {
 throw new ConnectTransportException(node; "invalid DiscoveryNode server_name [" + configuredServerName + "]"; e);
 } else {
 serverName = null;