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 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 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 and 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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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() + ")");
        }
    }




 

Optimize Elasticsearch Performance

Try The Tool