Briefly, this error occurs when an Elasticsearch node tries to refresh alerts from a node that is not the currently elected master. This is typically due to a misconfiguration in the cluster settings. To resolve this issue, you can ensure that all nodes are correctly configured to communicate with the master node. Additionally, check the health of the master node and ensure it’s functioning properly. If the problem persists, consider re-electing a new master node.
This guide will help you check for common problems that cause the log ” Cannot refresh alerts from nodes other than currently elected master. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, master, refresh.
Log Context
Log “Cannot refresh alerts from nodes other than currently elected master.” class name is LocalExporter.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
// no errors reported; no tasks to run; nothing currently installing.
listener.accept(ExporterResourceStatus.ready(name(); TYPE));
}
}
} else {
throw new ElasticsearchException("Cannot refresh alerts from nodes other than currently elected master.");
}
} @Override
public void openBulk(final ActionListener listener) {
