Timed out while waiting for initial discovery state – timeout – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

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 nodes fail to form a cluster within the specified timeout period. This could be due to network issues, incorrect configuration, or slow system performance. To resolve this, you can increase the timeout value in the Elasticsearch configuration. Also, ensure that all nodes have the correct network configuration and are able to communicate with each other. If the system is slow, consider upgrading the hardware or optimizing the system for better performance.

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 ” timed out while waiting for initial discovery state – timeout: {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery, node.

Log Context

Log “timed out while waiting for initial discovery state – timeout: {}” classname is Node.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        latch.countDown();
                    }

                    @Override
                    public void onTimeout(TimeValue timeout) {
                        logger.warn("timed out while waiting for initial discovery state - timeout: {}"; initialStateTimeout);
                        latch.countDown();
                    }
                }; state -> state.nodes().getMasterNodeId() != null; initialStateTimeout);

                try {

 

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?