Discovery-file Failed to parse transport address from – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 5-5

Briefly, this error occurs when Elasticsearch fails to parse the transport address from the discovery file. This could be due to incorrect syntax, wrong IP address, or port number in the discovery file. To resolve this, ensure the transport address is correctly formatted in the discovery file. Check for any typos or incorrect IP addresses or port numbers. Also, ensure the correct use of syntax, such as commas and colons. If the problem persists, consider resetting the transport address to its default settings.

This guide will help you check for common problems that cause the log ” [discovery-file] Failed to parse transport address from [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, discovery-file, hosts and plugins.

Log Context

Log “[discovery-file] Failed to parse transport address from [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

for (final String host : hostsList) {
            try {
                discoNodes.addAll(resolveDiscoveryNodes(host; 1; transportService;
                    () -> UNICAST_HOST_PREFIX + nodeIdGenerator.incrementAndGet() + "#"));
            } catch (IllegalArgumentException e) {
                logger.warn((Supplier>) () -> new ParameterizedMessage("[discovery-file] Failed to parse transport address from [{}]";
                                                                            host); 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?