You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2019/02/05 15:44:00 UTC

[jira] [Created] (IGNITE-11214) IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"

Alexey Goncharuk created IGNITE-11214:
-----------------------------------------

             Summary: IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"
                 Key: IGNITE-11214
                 URL: https://issues.apache.org/jira/browse/IGNITE-11214
             Project: Ignite
          Issue Type: Test
            Reporter: Alexey Goncharuk
             Fix For: 2.8


In the test local node does not have a cache started, but calls {{affinity.map...}} which causes the node to fetch affinity from the cluster. Due to a race the local node may observe {{readyAffinityVer ==  AffinityTopologyVersion(1,0)}} which is fine, but it requests the affinity using this topology version, which results in a missed affinity exception.

Suggested solution is to use {{max(readyAffinityVersion, discovery.topologyVersionEx)}} when fetching affinity from remote nodes (a node does not have the cache context started). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)