Received a cluster state uuid/v from a different master than the current one; – How to solve related issues

Average Read Time

2 Mins

Received a cluster state uuid/v from a different master than the current one; – How to solve related issues

Opster Team

Jan-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 uuid/v from a different master than the current one; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, discovery, master and queue.

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




 

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

Analyze your cluster

Skip to content