Failed to add ; address – How to solve related issues

Average Read Time

2 Mins

Failed to add ; address – 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 ” Failed to add ; address ” 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-gce, hosts and plugins.

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

{{mpg_logstarted}}

Log “Failed to add {}; address {}” classname is GceUnicastHostsProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                             cachedDynamicHosts.add(transportAddress);
                        }
                    }
                } catch (Exception e) {
                    final String finalIpPrivate = ip_private;
                    logger.warn((Supplier>) () -> new ParameterizedMessage("failed to add {}; address {}"; name; finalIpPrivate); e);
                }

            }
        } catch (Exception e) {
            logger.warn("exception caught during discovery"; e);




 

Run the Check-Up to get a customized report like this:

Analyze your cluster