Briefly, this error occurs when an Elasticsearch node that is not the master node attempts to update the cluster state. This is not allowed as only the master node should update the cluster state. To resolve this issue, ensure that only the master node is updating the cluster state. Check your cluster’s health and configuration. If there are network partitions, resolve them. If the master node is not functioning properly, fix the issues or elect a new master node. Also, ensure that your Elasticsearch version does not have bugs related to this issue.
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
[ratemypost]