Only allow reconfiguration while not already reconfiguring – How to solve this Elasticsearch error

Average Read Time

2 Mins

Only allow reconfiguration while not already reconfiguring – 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 ” only allow reconfiguration while not already reconfiguring ” 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 “only allow reconfiguration while not already reconfiguring”classname  is CoordinationState.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

} 
 if (clusterState.getLastAcceptedConfiguration().equals(getLastAcceptedConfiguration()) == false
 && getLastCommittedConfiguration().equals(getLastAcceptedConfiguration()) == false) {
 logger.debug("handleClientValue: only allow reconfiguration while not already reconfiguring");
 throw new CoordinationStateRejectedException("only allow reconfiguration while not already reconfiguring");
 }
 if (joinVotesHaveQuorumFor(clusterState.getLastAcceptedConfiguration()) == false) {
 logger.debug("handleClientValue: only allow reconfiguration if joinVotes have quorum for new config");
 throw new CoordinationStateRejectedException("only allow reconfiguration if joinVotes have quorum for new config");
 }

 

Watch a demo of the Check-Up:

Analyze your cluster

Skip to content