Exception caught during discovery: – How to solve related issues

Opster Team

Feb-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 ” Exception caught during discovery: ” to appear. To understand the issues related to this log, read the explanation below about the following 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 to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

                     logger.warn("failed to add {}; address {}"; e; name; ip_private);

        } catch (Throwable e) {
            logger.warn("Exception caught during discovery: {}"; e; e.getMessage());

        logger.debug("{} node(s) added"; cachedDiscoNodes.size());
        logger.debug("using dynamic discovery nodes {}"; cachedDiscoNodes);


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content