How To Solve Issues Related to Log – Waited for and no initial state was set by the discovery

Get an Elasticsearch Check-Up


Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

ES Check Up
Elasticsearch Error Guide In Page Navigation :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check My Elasticsearch 


Troubleshooting background

To troubleshoot Elasticsearch log “Waited for and no initial state was set by the discovery” it’s important to know common problems related to Elasticsearch concepts: discovery. See below-detailed explanations complete with common problems, examples and useful tips.


To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

waited for 30s and no inital state set by the discorery error run ElasticSearch 1.3.2 on ubuntu
stackoverflow.com/questions/25659738/waited-for-30s-and-no-inital-state-set-by-the-discorery-error-run-elasticsearch

Number of Views : 0.84 K  Score on Stackoverflow : 2

Elasticsearch 2.1.1 on localhost Java client error: MasterNotDiscoveredException[waited for [30s]]
stackoverflow.com/questions/34689921/elasticsearch-2-1-1-on-localhost-java-client-error-masternotdiscoveredexception

Number of Views : 1.75 K  Score on Stackoverflow : 3


Log Context

Log ”Waited for and no initial state was set by the discovery” classname is DiscoveryService.java
We have extracted the following from Elasticsearch source code to get 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");
        }






About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?