How To Solve Issues Related to Log – Received a cluster state from a different master then the current one; rejecting (received ; current )

Get an Elasticsearch Check-Up

Check if your ES issues are caused from misconfigured settings
(Free 2 min process)

ES Check Up
Elasticsearch Error Guide In Page Navigation :

Troubleshooting Background – start here to get the full picture       
Related Issues – selected resources on related issues  
Log Context – usefull for experts
About Opster – offering a diffrent approach to troubleshoot Elasticsearch

Check My Elasticsearch 

Troubleshooting background

To troubleshoot Elasticsearch log “Received a cluster state from a different master then the current one; rejecting (received ; current )” it’s important to know common problems related to Elasticsearch concepts: cluster, discovery, master. See below-detailed explanations complete with common problems, examples and useful tips.

Cluster in Elasticsearch

What is it

In Elasticsearch a cluster is a collection of one or more nodes (servers / VMs). A cluster can consist of an unlimited number of nodes. The cluster provides interface for indexing and storing data and search capability across all of the data which is stored in the data nodes

Each cluster has a single master node that is elected by the master eligible nodes. In cases where the master is not available the other connected master eligible nodes elect a new master. Clusters are identified by a unique name, which defaults to “Elasticsearch”.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

Master Goes Down Even After Re Elec


Elasicsearc Multi Rack Configuratio


Log Context

Log ”Received a cluster state from a different master then the current one; rejecting (received ; current )” classname is
We have extracted the following from Elasticsearch source code to get an in-depth context :

<pre class="wp-block-syntaxhighlighter-code">     static boolean shouldIgnoreOrRejectNewClusterState(ESLogger logger; ClusterState currentState; ClusterState newClusterState) {
        if (currentState.nodes().masterNodeId() == null) {
            return false;
        if (!currentState.nodes().masterNodeId().equals(newClusterState.nodes().masterNodeId())) {
            logger.warn("received a cluster state from a different master then the current one; rejecting (received {}; current {})"; newClusterState.nodes().masterNode(); currentState.nodes().masterNode());
            throw new IllegalStateException("cluster state from a different master than the current one; rejecting (received " + newClusterState.nodes().masterNode() + "; current " + currentState.nodes().masterNode() + ")");
        } else if (newClusterState.version() < currentState.version()) {
            // if the new state has a smaller version; and it has the same master node; then no need to process it
            logger.debug("received a cluster state that has a lower version than the current one; ignoring (received {}; current {})"; newClusterState.version(); currentState.version());
            return true;


About Opster

Incorporating deep knowledge and broad history of Elasticsearch issues. Opster’s solution identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to manage, troubleshoot and prevent issues

We are constantly updating our analysis of Elasticsearch logs, errors, and exceptions. Sharing best practices and providing troubleshooting guides.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster

Did this page help you?