No longer master. source: ” + source + ” – 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. source: ” + source + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: master and cluster.

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

 * called when the task was rejected because the local node is no longer master.
 * Used only for tasks submitted to {@link MasterService}.
 default void onNoLongerMaster(String source) {
 onFailure(source; new NotMasterException("no longer master. source: [" + source + "]"));
 * Called when the result of the {@link ClusterStateTaskExecutor#execute(ClusterState; List)} have been processed
 * properly by all listeners.


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content