Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues causing many log errors (free and no installation required)
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, 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 discover the cause of many errors and provides suitable actionable recommendations.
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
Related issues to this log
We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :
1 Network Interruption Some Nodes Not
2 Very Weird Es Cluster State Problem
About Opster
Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.
