Mixed-version cluster join validation on cluster state – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-7.11

Briefly, this error occurs when you are trying to add a node with a different Elasticsearch version to an existing cluster. Elasticsearch requires all nodes in a cluster to run on the same version to ensure compatibility and prevent issues. To resolve this, you can either upgrade the node to match the cluster’s version or downgrade the cluster to match the node’s version. Alternatively, you can create a new cluster with the different version node and migrate the data.

This guide will help you check for common problems that cause the log ” mixed-version cluster join validation on cluster state ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: join, cluster.

Log Context

Log “mixed-version cluster join validation on cluster state” class name is JoinHelper.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ThreadPool.Names.GENERIC; ValidateJoinRequest::new;
 (request; channel; task) -> {
 final ClusterState localState = currentStateSupplier.get();
 if (localState.metadata().clusterUUIDCommitted() &&
 localState.metadata().clusterUUID().equals(request.getState().metadata().clusterUUID()) == false) {
 throw new CoordinationStateRejectedException("mixed-version cluster join validation on cluster state" +
 " with a different cluster uuid " + request.getState().metadata().clusterUUID() +
 " than local cluster uuid " + localState.metadata().clusterUUID()
 + "; rejecting");
 joinValidators.forEach(action -> action.accept(transportService.getLocalNode(); request.getState()));


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?