Re: Failed to add node to topology because it has the same hash code for partitioned affinity as one of existing nodes

[kvenkatramtreddy]

Hi It is having unique consistentId across cluster. All nodes running for
some time, it is happening after some time.Please see the discoverySpi and
consistenId details below.
*Node1 ConsistentId (Server 1):*
                                                                                
                                                                                
                                                                                
         
127.0.0.1:48500..48520                               
192.168.0.4:48500..48520                               
192.168.0.5:48500..48520                                                        
                                                    
Node2 ConsistentId (Server 1):
                                                                                
                                                                                
                                                                                
             
127.0.0.1:48500..48520                               
192.168.0.4:48500..48520                               
192.168.0.5:48500..48520                                                        
                                                            
Node 3(server2):
                                                                                
                                                                                
                                                                                
             
127.0.0.1:48500..48520                               
192.168.0.4:48500..48520                               
192.168.0.5:48500..48520                                                        
                                                    



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/