Log Exception caught during discovery: – How To Solve Related Issues

Log 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 try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)


This guide will help you check for common problems that cause the log “Exception caught during discovery:” 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, 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 discover the cause of many errors and provides suitable actionable recommendations. 

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


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 :


Github Issue Number 16967  


About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now