Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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. Take a self-guided product tour to see for yourself (no registration required).
This guide will help you check for common problems that cause the log ” Master should not receive new cluster state from ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster and master.
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
