Log Master left ; reason – How To Solve Related Issues



Log Master left ; reason – How To Solve Related Issues

Opster Team

Dec-19, 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 “Master left ; reason” 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: discovery-azure-classic.


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”Master left [{}]; reason [{}]” classname is ZenDiscovery.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (localNodeMaster()) {
            // we might get this on both a master telling us shutting down; and then the disconnect failure
            return;
        }

        logger.info(() -> new ParameterizedMessage("master_left [{}]; reason [{}]"; masterNode; reason); cause);

        synchronized (stateMutex) {
            if (localNodeMaster() == false && masterNode.equals(committedState.get().nodes().getMasterNode())) {
                // flush any pending cluster states from old master; so it will not be set as master again
                pendingStatesQueue.failAllStatesAndClear(new ElasticsearchException("master left [{}]"; reason));

 

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 Discovery Zen Masters Alicia Master  

User Authentication And Xpack Probl  

 

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