You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by kvenkatramtreddy <kv...@gmail.com> on 2018/08/07 04:27:44 UTC
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
<property name="affinity">
<bean
class="org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction">
<property name="excludeNeighbors" value="true"/>
</bean>
</property>
Receiving the Failed to add node to topology error after some time. Please
could you help us to resolve this issue.
igniteSamehashError.txt
<http://apache-ignite-users.70518.x6.nabble.com/file/t1700/igniteSamehashError.txt>
Thanks & Regards,
Venkat
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Failed to add node to topology because it has the same hash code
for partitioned affinity as one of existing nodes
Posted by Вячеслав Коптилин <sl...@gmail.com>.
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 <kv...@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.
>
Re: Failed to add node to topology because it has the same hash
code for partitioned affinity as one of existing nodes
Posted by kvenkatramtreddy <kv...@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: http://apache-ignite-users.70518.x6.nabble.com/
Re: Failed to add node to topology because it has the same hash code
for partitioned affinity as one of existing nodes
Posted by Вячеслав Коптилин <sl...@gmail.com>.
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 <kv...@gmail.com>:
> 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
> <property name="affinity">
> <bean
>
> class="org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction">
> <property name="excludeNeighbors"
> value="true"/>
> </bean>
> </property>
>
> Receiving the Failed to add node to topology error after some time. Please
> could you help us to resolve this issue.
>
> igniteSamehashError.txt
> <
> http://apache-ignite-users.70518.x6.nabble.com/file/t1700/igniteSamehashError.txt>
>
>
> Thanks & Regards,
> Venkat
>
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>