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

Hello, > Hi It is having unique consistentId across cluster. > 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):

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

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):*

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

Hello, It seems that there are nodes that have the same value of consistentId property. Please try to set IgniteConfiguration.setConsistentId to a unique value cluster-wide. Thanks. вт, 7 авг. 2018 г. в 7:27, kvenkatramtreddy : > Hi Team, > > I have configured my all caches replicated mode

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

Hi Team, I have configured my all caches replicated mode with native persistence enable and running it on 3 nodes. 2 nodes runs on same server and another node run on different server. I have configured unique consistentId for each node and unique IGNITE_HOME. I also configured