Exception thrown by listener while notifying no longer master from – 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. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Exception thrown by listener while notifying no longer master from ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and master.

Log Context

Log “exception thrown by listener while notifying no longer master from [{}]” classname is InternalClusterService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         
Override
        public void onNoLongerMaster(String source) {
            try {
                listener.onNoLongerMaster(source);
            } catch (Exception e) {
                logger.error("exception thrown by listener while notifying no longer master from [{}]"; e; source);
            }
        }

        
Override
        public void clusterStateProcessed(String source; ClusterState oldState; ClusterState newState) {


 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content