Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” no longer master ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: master.
Log Context
Log “no longer master”classname is SnapshotsService.java 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);
