Waited for and no initial state was set by the discovery – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Waited for and no initial state was set by the discovery ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “waited for {} and no initial state was set by the discovery” classname is DiscoveryService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 
    public void joinClusterAndWaitForInitialState() {
        try {
            discovery.startInitialJoin();
            if (!initialStateListener.waitForInitialState(initialStateTimeout)) {
                logger.warn("waited for {} and no initial state was set by the discovery"; initialStateTimeout);
            }
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
            throw new ElasticsearchTimeoutException("Interrupted while waiting for initial discovery state");
        }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content