Cannot start publishing next value before accepting previous one – How to solve this Elasticsearch error

Average Read Time

2 Mins

Cannot start publishing next value before accepting previous one – 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 ” cannot start publishing next value before accepting previous one ” 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 “cannot start publishing next value before accepting previous one”classname  is CoordinationState.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

logger.debug("handleClientValue: ignored request as election not won");
 throw new CoordinationStateRejectedException("election not won");
 }
 if (lastPublishedVersion != getLastAcceptedVersion()) {
 logger.debug("handleClientValue: cannot start publishing next value before accepting previous one");
 throw new CoordinationStateRejectedException("cannot start publishing next value before accepting previous one");
 }
 if (clusterState.term() != getCurrentTerm()) {
 logger.debug("handleClientValue: ignored request due to term mismatch " +
 "(expected: [term {} version >{}]; actual: [term {} version {}])";
 getCurrentTerm(); lastPublishedVersion; clusterState.term(); clusterState.version());

 

Watch a demo of the Check-Up:

Analyze your cluster