Can not convert to transport address. skipping. – How to solve related issues

Average Read Time

2 Mins

Can not convert to transport address. skipping. – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

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

This guide will help you check for common problems that cause the log ” Can not convert to transport address. skipping. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, discovery-azure-classic, hosts, plugins and repository-azure.

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 “Can not convert [{}] to transport address. skipping. [{}]” classname is AzureUnicastHostsProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     for (TransportAddress address : addresses) {
                        logger.trace("adding {}; transport_address {}"; networkAddress; address);
                        dynamicHosts.add(address);
                    }
                } catch (Exception e) {
                    logger.warn("can not convert [{}] to transport address. skipping. [{}]"; networkAddress; e.getMessage());
                }
            }
        }

        logger.debug("{} addresses added"; dynamicHosts.size());




 

Run the Check-Up to get customized insights on your system:

Analyze your cluster