Exception caught during discovery – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch nodes fail to discover each other in a cluster. This could be due to network issues, incorrect configuration of discovery settings, or firewall blocking the communication. To resolve this, ensure that the network is functioning properly, check the discovery settings in the Elasticsearch configuration file, and verify that the firewall is not blocking the required ports. Also, ensure that the nodes are running the same version of Elasticsearch.

This guide will help you check for common problems that cause the log ” exception caught during discovery ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugins, discovery-gce, discovery.

Log Context

Log “exception caught during discovery” classname is GceSeedHostsProvider.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    logger.warn(() -> format("failed to add %s; address %s"; name; finalIpPrivate); e);

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

        logger.debug("{} addresses added"; cachedDynamicHosts.size());
        logger.debug("using transport addresses {}"; cachedDynamicHosts);


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?