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

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

Updated: Feb-20

Elasticsearch Version: 1.7-8.0

Background

To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 


To troubleshoot log “Exception caught during discovery:” it’s important to understand a few problems related to Elasticsearch concepts discovery, discovery-gce, hosts, plugins. See bellow important tips and explanations on these concepts

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 detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now