How To Solve Issues Related to Log – Master should not receive new cluster state from

Prevent Your Next ELK Incident

Try our free Check Up to test if your ES issues are caused from misconfigured settings

Fix Issue

Updated: Feb-20

In-Page Navigation (click to jump) :

Opster Offer’s World-Class Elasticsearch Expertise In One Powerful Product
Try Our Free ES Check-Up   Prevent Incident

Troubleshooting background

To troubleshoot Elasticsearch log “Master should not receive new cluster state from” it’s important to understand common problems related to Elasticsearch concepts: cluster, master. See detailed explanations below complete with common problems, examples and useful tips.

To help troubleshoot related issues we have gathered selected Q&A from the community and issues from Github , please review the following for further information :

1 Network Interruption Some Nodes Not  

2Very Weird Es Cluster State Problem  

Log Context

Log ”master should not receive new cluster state from [{}]” classname is
We have extracted the following from Elasticsearch source code to get an in-depth context :

     private class UpdateClusterStateListener implements PublishRiverClusterStateAction.NewClusterStateListener {
        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());

            submitStateUpdateTask("received_state"; new RiverClusterStateUpdateTask() {

About Opster

Opster identifies and predicts root causes of Elasticsearch problems, provides recommendations and can automatically perform various actions to prevent issues, optimize performance and save resources.

Learn more: Glossary | Blog| Troubleshooting guides | Error Repository

Need help with any Elasticsearch issue ? Contact Opster