No discovery configuration found will perform best-effort cluster bootstrapping after – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch cannot find a discovery configuration, which is essential for the nodes to form a cluster. It’s trying to bootstrap the cluster with the available nodes. To resolve this, ensure that the discovery configuration is correctly set in the elasticsearch.yml file. This includes specifying the discovery.seed_hosts and cluster.initial_master_nodes. Also, check the network connectivity between the nodes and ensure that the Elasticsearch service is running on all nodes. If the issue persists, consider restarting the Elasticsearch service on all nodes.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

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: cluster, 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?