Rejecting join since this node has not received its initial configuration yet – 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 ” rejecting join since this node has not received its initial configuration yet ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: join, node and 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 “rejecting join since this node has not received its initial configuration yet”classname  is CoordinationState.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// We do not check for an election won on setting the initial configuration; so it would be possible to end up in a state where
 // we have enough join votes to have won the election immediately on setting the initial configuration. It'd be quite
 // complicated to restore all the appropriate invariants when setting the initial configuration (it's not just electionWon)
 // so instead we just reject join votes received prior to receiving the initial configuration.
 logger.debug("handleJoin: rejecting join since this node has not received its initial configuration yet");
 throw new CoordinationStateRejectedException("rejecting join since this node has not received its initial configuration yet");
 } 
 boolean added = joinVotes.addJoinVote(join);
 boolean prevElectionWon = electionWon;
 electionWon = isElectionQuorum(joinVotes);

 

Try AutoOps to detect and fix issues in your cluster:

Analyze Your Cluster

Skip to content