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

Opster Team

August-23, Version: 7-8.9

Briefly, this error occurs when an attempt is made to reconfigure Elasticsearch while it’s already in the process of reconfiguration. This is not allowed as it can lead to inconsistencies and errors. To resolve this issue, you can either wait for the current reconfiguration process to complete before initiating a new one, or you can stop the current reconfiguration process and then start the new one. It’s also important to ensure that automated processes or scripts are not simultaneously attempting to reconfigure Elasticsearch.

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.

Log Context

Log “only allow reconfiguration while not already reconfiguring” class name is CoordinationState.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 );
 }  if (electionStrategy.isInvalidReconfiguration(clusterState; getLastAcceptedConfiguration(); getLastCommittedConfiguration())) {
 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");
 }

 

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?