No longer master – How to solve this Elasticsearch error

Average Read Time

2 Mins

No longer master – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” no longer master ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: master.

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 “no longer master”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

// We have snapshot listeners but are not the master any more. Fail all waiting listeners except for those that already
 // have their snapshots finalizing (those that are already finalizing will fail on their own from to update the cluster
 // state).
 for (Snapshot snapshot : Set.copyOf(snapshotCompletionListeners.keySet())) {
 if (endingSnapshots.add(snapshot)) {
 failSnapshotCompletionListeners(snapshot; new SnapshotException(snapshot; "no longer master"));
 } catch (Exception e) {
 assert false : new AssertionError(e);


Watch a demo of the Check-Up:

Analyze your cluster