Log Masterleft ; reason – How To Solve Related Issues


Log Masterleft ; reason – 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 ” Masterleft ; 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.

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 “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));




 

Optimize Elasticsearch Performance

Try The Tool