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

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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 a customized report like this:

Analyze your cluster