Incoming cluster state version – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-7.15

Briefly, this error occurs when there is a mismatch between the cluster state versions of the nodes in an Elasticsearch cluster. This could be due to a node rejoining the cluster after a network partition or due to a failed cluster state update. To resolve this issue, you can try restarting the Elasticsearch service on the affected nodes. If the problem persists, consider rolling back to a previous cluster state version or updating all nodes to the same Elasticsearch version.

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: cluster, version.

Log Context

Log “incoming cluster state version” class name 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) {


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?