How To Solve Issues Related to Log – Received a cluster state uuid/v from a different master than the current one;

How To Solve Issues Related to Log – Received a cluster state uuid/v from a different master than the current one;

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 a cluster state uuid/v from a different master than the current one;” it’s important to understand a few problems related to Elasticsearch concepts cluster, discovery, master, queue. See bellow important tips and explanations on these concepts

Log Context

Log”Received a cluster state (uuid[{}]/v[{}]) from a different master than the current one;” classname is PendingClusterStatesQueue.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             final DiscoveryNode pendingMasterNode = pendingState.nodes().getMasterNode();
            if (Objects.equals(currentMaster; pendingMasterNode) == false) {
                contextsToRemove.add(pendingContext);
                if (pendingContext.committed()) {
                    // this is a committed state ; warn
                    logger.warn("received a cluster state (uuid[{}]/v[{}]) from a different master than the current one;"
                        + " rejecting (received {}; current {})";
                            pendingState.stateUUID(); pendingState.version(); pendingMasterNode; currentMaster);
                    pendingContext.listener.onNewClusterStateFailed(
                            new IllegalStateException("cluster state from a different master than the current one;" +
                                " rejecting (received " + pendingMasterNode + "; current " + currentMaster + ")"));




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 Elasticsearch 7 Cluster Setup With  

Elasicsearc Multi Rack Configuratio  

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