ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-10821) Caching affinity with affinity similarity key is broken
Date Tue, 15 Jan 2019 05:31:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Kovalenko reassigned IGNITE-10821:
----------------------------------------

    Assignee:     (was: Pavel Kovalenko)

> 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.8
>
>
> 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
(v7.6.3#76005)

Mime
View raw message