Log Received a join request for an existing node – How To Solve Related Issues



Log Received a join request for an existing node – How To Solve Related Issues

Opster Team

Feb-20, Version: 1.7-8.0



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 “Received a join request for an existing node” 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: discovery, join, node, request.


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”received a join request for an existing node [{}]” classname is ZenDiscovery.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             clusterService.submitStateUpdateTask("zen-disco-receive(join from node[" + node + "])"; Priority.IMMEDIATE; new ProcessedClusterStateUpdateTask() {
                
Override
                public ClusterState execute(ClusterState currentState) {
                    if (currentState.nodes().nodeExists(node.id())) {
                        // the node already exists in the cluster
                        logger.info("received a join request for an existing node [{}]"; node);
                        // still send a new cluster state; so it will be re published and possibly update the other node
                        return ClusterState.builder(currentState).build();
                    }
                    DiscoveryNodes.Builder builder = DiscoveryNodes.builder(currentState.nodes());
                    for (DiscoveryNode existingNode : currentState.nodes()) {



 

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 Nodes won’t join cluster : NotMasterException (Weird master election bug) -views 2.58 K ,score 5

Github Issue Number 8242  

 

About Opster

Opster line of products and support services detects, prevents, optimizes and automates everything needed to manage mission-critical Elasticsearch.

Find Configuration Errors

Analyze Now