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

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

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


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((Supplier>) () -> new ParameterizedMessage("failed to add {}; address {}"; 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);





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 :

1 elasticsearch kubernetes plugin issue

0.43 K 

Elasticsearch error failed to connect to master – no route to host

  14.40 K 10

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now