[
https://issues.apache.org/jira/browse/IGNITE-12618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030486#comment-17030486
]
Ignite TC Bot commented on IGNITE-12618:
----------------------------------------
{panel:title=Branch: [pull/7359/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4986152&buildTypeId=IgniteTests24Java8_RunAll]
> Affinity cache for version of last server event can be wiped from history
> -------------------------------------------------------------------------
>
> Key: IGNITE-12618
> URL: https://issues.apache.org/jira/browse/IGNITE-12618
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.8
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After IGNITE-11465 implemented, there's still a corner case when we can get
> "Getting affinity for topology version earlier than affinity is calculated"
> error.
> If the whole history (not more than
> GridAffinityAssignmentCache#MAX_HIST_LINKS_SIZE entries) consists of shallow
> copies for client events, we may be not able to fetch affinity cache for last
> affinity change version.
> We need to make GridAffinityAssignmentCache#cachedAffinity work if affinity
> version no less than [last affinity change version] is passed as an argument.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
