Interrupted while waiting for initial discovery state – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch is unable to complete its initial discovery phase due to an interruption. This could be due to network issues, incorrect configuration, or unavailability of nodes. To resolve this, ensure that your network is stable and all nodes are up and running. Check your Elasticsearch configuration for any errors, particularly in the discovery settings. If you’re using a cluster, ensure all nodes are correctly configured and can communicate with each other.

This guide will help you check for common problems that cause the log ” Interrupted while waiting for initial discovery state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: node, discovery.

Log Context

Log “Interrupted while waiting for initial discovery state” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }; state -> state.nodes().getMasterNodeId() != null; initialStateTimeout);  try {
 } catch (InterruptedException e) {
 throw new ElasticsearchTimeoutException("Interrupted while waiting for initial discovery state");
 }  injector.getInstance(HttpServerTransport.class).start();