How To Solve Issues Related to Log – Can not convert to transport address. skipping.

How To Solve Issues Related to Log – Can not convert to transport address. skipping.

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Can not convert to transport address. skipping.” it’s important to understand a few problems related to Elasticsearch concepts discovery, discovery-azure-classic, hosts, plugins, repository-azure. See bellow important tips and explanations on these concepts

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());




Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Elasticsearch RestHighLevelClient missing transitive dependencies

3.76 K 3

how to move elasticsearch data from one server to another

  92.35 K 78

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now