Incoming cluster state version – 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 ” incoming cluster state version ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: version 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 “incoming cluster state version”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (clusterState.version() <= lastPublishedVersion) {
 logger.debug("handleClientValue: ignored request due to version mismatch " +
 "(expected: [term {} version >{}]; actual: [term {} version {}])";
 getCurrentTerm(); lastPublishedVersion; clusterState.term(); clusterState.version());
 throw new CoordinationStateRejectedException("incoming cluster state version " + clusterState.version() +
 " lower or equal to last published version " + lastPublishedVersion);
 if (clusterState.getLastAcceptedConfiguration().equals(getLastAcceptedConfiguration()) == false
 && getLastCommittedConfiguration().equals(getLastAcceptedConfiguration()) == false) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content