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



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

Opster Team

Jan-20, Version: 1.7-8.0



Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many log errors (free and no installation required)

 

This guide will help you check for common problems that cause the log “Received a cluster state from a different master than the current one; rejecting received ; current” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: cluster, discovery, master.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations. 

Log Context

Log”Received a cluster state from a different master than 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 :

     public static void validateStateIsFromCurrentMaster(Logger logger; DiscoveryNodes currentNodes; ClusterState newClusterState) {
        if (currentNodes.getMasterNodeId() == null) {
            return;
        }
        if (!currentNodes.getMasterNodeId().equals(newClusterState.nodes().getMasterNodeId())) {
            logger.warn("received a cluster state from a different master than the current one; rejecting (received {}; current {})";
                newClusterState.nodes().getMasterNode(); currentNodes.getMasterNode());
            throw new IllegalStateException("cluster state from a different master than the current one; rejecting (received " +
                newClusterState.nodes().getMasterNode() + "; current " + currentNodes.getMasterNode() + ")");
        }
    }




 

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Master Goes Down Even After Re Elec  

Elasicsearc Multi Rack Configuratio  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now