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):               127.0.0.1:48500..48520 192.168.0.4:48500..48520
192.168.0.5:48500..48520

Hmm, all these strings are absolutely the same :), and it looks like that
it is the root cause of the issue.

Thanks.


вт, 7 авг. 2018 г. в 13:41, kvenkatramtreddy <kvenkatramtre...@gmail.com>:

> 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 the Apache Ignite Users mailing list archive
> <http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com.
>