Before you begin reading this guide, we recommend you run 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 ” Master should not receive new cluster state from ” 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: cluster and master.
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 “master should not receive new cluster state from [{}]” classname is RiverClusterService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
private class UpdateClusterStateListener implements PublishRiverClusterStateAction.NewClusterStateListener {
Override
public void onNewClusterState(final RiverClusterState clusterState) {
ClusterState state = clusterService.state();
if (state.nodes().localNodeMaster()) {
logger.warn("master should not receive new cluster state from [{}]"; state.nodes().masterNode());
return;
}
submitStateUpdateTask("received_state"; new RiverClusterStateUpdateTask() {
Override
Run the Check-Up to get customized recommendations like this:
Run Check-Up
The high disk watermark threshold is about to be reached in specific nodes
Description
There are various “watermark” thresholds on each Elasticsearch cluster. When the high disk watermark threshold has been exceeded, it means disk space is running out. The node will…
Recommendations
Based on your specific ES deployment you should…
X-PUT curl -H [a customized code snippet to resolve the issue]