Failed to add address – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.3

Briefly, this error occurs when Elasticsearch is unable to add an IP address to the list of nodes it can communicate with. This could be due to network issues, incorrect configuration, or the target node being down. To resolve this, you can check the network connectivity, ensure the IP address and port are correctly configured, and verify that the target node is up and running. Also, check the Elasticsearch logs for more detailed error information.

This guide will help you check for common problems that cause the log ” failed to add {}; address {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery-gce, plugins, discovery.

Log Context

Log “failed to add {}; address {}” classname is GceSeedHostsProvider.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);

 

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?