How To Solve Issues Related to Log – Received cluster state from which is also master but with a different cluster name

How To Solve Issues Related to Log – Received cluster state from which is also master but with a different cluster name

Updated: Jan-20

Elasticsearch Version: 1.7-8.0

Background

Before you begin reading this guide try our beta Elasticsearch Health Check-Up it analyses JSON’s to provide personalized recommendations that can improve your clusters performance.


To troubleshoot log “Received cluster state from which is also master but with a different cluster name” it’s important to understand a few problems related to Elasticsearch concepts cluster, discovery, master. See bellow important tips and explanations on these concepts

Log Context

Log”Received cluster state from [{}] which is also master but with a different cluster name [{}]” classname is ZenDiscovery.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

      * does simple sanity check of the incoming cluster state. Throws an exception on rejections.
     */
    static void validateIncomingState(Logger logger; ClusterState incomingState; ClusterState lastState) {
        final ClusterName incomingClusterName = incomingState.getClusterName();
        if (!incomingClusterName.equals(lastState.getClusterName())) {
            logger.warn("received cluster state from [{}] which is also master but with a different cluster name [{}]";
                incomingState.nodes().getMasterNode(); incomingClusterName);
            throw new IllegalStateException("received state from a node that is not part of the cluster");
        }
        if (lastState.nodes().getLocalNode().equals(incomingState.nodes().getLocalNode()) == false) {
            logger.warn("received a cluster state from [{}] and not part of the cluster; should not happen";




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 Elasicsearc Multi Rack Configuratio  

Whats Happend My Es Cluster Plz Hel  

About Opster

Opster detects root causes of Elasticsearch problems, provides automated recommendations and can perform various actions to prevent issues and optimize performance

Find Configuration Errors

Analyze Now