[jira] [Commented] (IGNITE-10821) Caching affinity with affinity similarity key is broken

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946838#comment-16946838 ] 

Maxim Muzafarov commented on IGNITE-10821:
------------------------------------------

Moved to 2.9 due to inactivity. Please, feel free to move it back if you will be able to complete the ticket by 2.8 code freeze date, December 2, 2019.

> Caching affinity with affinity similarity key is broken
> -------------------------------------------------------
>
>                 Key: IGNITE-10821
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10821
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.8
>            Reporter: Pavel Kovalenko
>            Priority: Major
>             Fix For: 2.9
>
>
> When some cache groups have the same affinity function, number of partitions, backups and the same node filter they can use the same affinity distribution without needs for explicit recalculating. These parameters are called as "Affinity similarity key". 
> In case of affinity recalculation caching affinity using this key may speed-up the process.
> However, after https://issues.apache.org/jira/browse/IGNITE-9561 merge this mechanishm become broken, because parallell execution of affinity recalculation for the similar affinity groups leads to caching affinity misses.
> To fix it we should couple together similar affinity groups and run affinity recalculation for them in one thread, caching previous results.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)