Received cluster state from – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7-7.15

Briefly, this error occurs when a node in the Elasticsearch cluster receives a cluster state from a node that is not the master node. This could be due to network issues, or the master node being temporarily unavailable. To resolve this issue, you can check the network connectivity between the nodes, ensure the master node is functioning properly, or consider increasing the ‘’ timeout if the network is slow. Also, check the cluster health and ensure all nodes are properly connected to the master node.

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

Log Context

Log “received cluster state from” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (localState.metadata().clusterUUIDCommitted() &&
 localState.metadata().clusterUUID().equals(publishRequest.getAcceptedState().metadata().clusterUUID()) == false) {
 logger.warn("received cluster state from {} with a different cluster uuid {} than local cluster uuid {}; rejecting";
 sourceNode; publishRequest.getAcceptedState().metadata().clusterUUID(); localState.metadata().clusterUUID());
 throw new CoordinationStateRejectedException("received cluster state from " + sourceNode +
 " with a different cluster uuid " + publishRequest.getAcceptedState().metadata().clusterUUID() +
 " than local cluster uuid " + localState.metadata().clusterUUID() + "; rejecting");
 }  if (publishRequest.getAcceptedState().term() > localState.term()) {


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?