[
https://issues.apache.org/jira/browse/IGNITE-7366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709736#comment-16709736
]
ASF GitHub Bot commented on IGNITE-7366:
----------------------------------------
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/3451
> 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
> Assignee: Pavel Pereslegin
> Priority: Major
> Fix For: 2.7
>
>
> When two nodes which are deploying services join at the same time, and
> exception is observed:
> {code}
> SEVERE: Error when executing service: null
> java.lang.IllegalStateException: Getting affinity for topology version
> earlier than affinity is calculated [locNode=TcpDiscoveryNode
> [id=245d4bec-0384-4808-b66d-d2340930207f..., discPort=37500, order=2,
> intOrder=2, lastExchangeTime=1515394551283, loc=true,
> ver=2.3.0#20171028-sha1:8add7fd5, isClient=false], grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0],
> head=AffinityTopologyVersion [topVer=4, minorTopVer=0],
> history=[AffinityTopologyVersion [topVer=2, minorTopVer=0],
> AffinityTopologyVersion [topVer=2, minorTopVer=1], AffinityTopologyVersion
> [topVer=4, minorTopVer=0]]]
> 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
(v7.6.3#76005)
