Received a cluster state from a different master then the current one; rejecting (received ; current ) – How to solve related issues

Average Read Time

2 Mins

Received a cluster state from a different master then the current one; rejecting (received ; current ) – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Received a cluster state from a different master then the current one; rejecting (received ; current ) ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, discovery and master.

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 “received a cluster state from a different master then the current one; rejecting (received {}; current {})” classname is ZenDiscovery.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     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() 

 

Run the free Check-Up to get customized insights on your system:

Analyze your cluster

Skip to content