Invalid DiscoveryNode server_name ” + configuredServerName + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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 and discovery.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “invalid DiscoveryNode server_name [” + configuredServerName + “]”classname  is SecurityNetty4Transport.java 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;
 }
 }

 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content