No longer master. source: ” + source + ” – How to solve this Elasticsearch error

Average Read Time

2 Mins

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 Error 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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the 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 which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

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.


Run the Check-Up to get a customized report like this:

Analyze your cluster