Master-left ; reason ES Log v2.3 – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Master-left ; reason ES Log v2.3 ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: discovery.


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("master_left [{}]; reason [{}]"; masterNode; reason);

        clusterService.submitStateUpdateTask("zen-disco-master_failed (" + masterNode + ")"; new ClusterStateUpdateTask(Priority.IMMEDIATE) {
            
Override
            public boolean runOnlyOnMaster() {
                return false;



 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content