Not enough nodes discovered to form a quorum in the initial configuration – How to solve this Elasticsearch error

Average Read Time

2 Mins

Not enough nodes discovered to form a quorum in the initial configuration – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” not enough nodes discovered to form a quorum in the initial configuration ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

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 “not enough nodes discovered to form a quorum in the initial configuration”classname  is Coordinator.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

peerFinder.getFoundPeers().forEach(knownNodes::add); 
 if (votingConfiguration.hasQuorum(knownNodes.stream().map(DiscoveryNode::getId).collect(Collectors.toList())) == false) {
 logger.debug("skip setting initial configuration as not enough nodes discovered to form a quorum in the " +
 "initial configuration [knownNodes={}; {}]"; knownNodes; votingConfiguration);
 throw new CoordinationStateRejectedException("not enough nodes discovered to form a quorum in the initial configuration " +
 "[knownNodes=" + knownNodes + "; " + votingConfiguration + "]");
 } 
 logger.info("setting initial configuration to {}"; votingConfiguration);
 final CoordinationMetadata coordinationMetadata = CoordinationMetadata.builder(currentState.coordinationMetadata())

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content