No discovery configuration found. will perform best-effort cluster bootstrapping after – 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 analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” No discovery configuration found. will perform best-effort cluster bootstrapping after ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: bootstrap, cluster and discovery.

Log Context

Log “no discovery configuration found; will perform best-effort cluster bootstrapping after [{}]” classname is ClusterBootstrapService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
        if (transportService.getLocalNode().isMasterNode() == false) {
            return;
        }

        logger.info("no discovery configuration found; will perform best-effort cluster bootstrapping after [{}] " +
            "unless existing master is discovered"; unconfiguredBootstrapTimeout);

        transportService.getThreadPool().scheduleUnlessShuttingDown(unconfiguredBootstrapTimeout; Names.GENERIC; new Runnable() {
            
Override
            public void run() {



 

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?

Analyze your cluster & get personalized recommendations

Skip to content