You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/02/06 16:05:00 UTC
[jira] [Commented] (IGNITE-11214)
IgniteCacheAtomicPutAllFailoverSelfTest fails with "Cannot find cache"
[ https://issues.apache.org/jira/browse/IGNITE-11214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761884#comment-16761884 ]
Ignite TC Bot commented on IGNITE-11214:
----------------------------------------
{panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3008158&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Assignee: Alexey Goncharuk
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)