Ilya Kasnacheev created IGNITE-7366:
---------------------------------------
Summary: Affinity assignment exception in service processor during
multiple nodes join
Key: IGNITE-7366
URL: https://issues.apache.org/jira/browse/IGNITE-7366
Project: Ignite
Issue Type: Bug
Components: compute
Affects Versions: 2.3
Reporter: Ilya Kasnacheev
When two nodes which are deploying services join at the same time, and
exception is observed:
{code}
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:514)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:419)
at
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:220)
at
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:256)
at
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:247)
at
org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:271)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$TopologyListener$1.run0(GridServiceProcessor.java:1771)
at
org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:1958)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
{code}
This may be caused by exchange merges. There are 4 nodes joining topology. When
nodes 3 and 4 join at the same time, exchanges for [3, 0] and [4, 0] are
merged. But, TopologyListener in service processor is notified about topVer [3,
0], for which there is no affinity because exchange has already moved forward
to [4, 0].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
