You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgenii Zhuravlev (JIRA)" <ji...@apache.org> on 2018/09/27 09:10:00 UTC
[jira] [Assigned] (IGNITE-5836) AffinityFunctionContext should
provide consistent previous assignment
[ https://issues.apache.org/jira/browse/IGNITE-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgenii Zhuravlev reassigned IGNITE-5836:
-----------------------------------------
Assignee: (was: Evgenii Zhuravlev)
> AffinityFunctionContext should provide consistent previous assignment
> ---------------------------------------------------------------------
>
> Key: IGNITE-5836
> URL: https://issues.apache.org/jira/browse/IGNITE-5836
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.0
> Reporter: Valentin Kulichenko
> Priority: Critical
> Labels: usability
> Fix For: 2.8
>
>
> Currently each cache maintains its own {{AffinityFunctionContext}}. This leads to the case that {{previousAssignment}} can be different for two caches created on different topology versions. In particular, this broke {{FairAffinityFunction}} which was removed because of that.
> We should do the following:
> * Make sure that {{previousAssignment}} is consistent for all caches with same affinity function, regardless of topology versions caches were created on.
> * Add mechanism to enforce equality check for affinity functions. We probably will need to force user to implement {{equals}} for cache node filter and backup filter.
> * When above is done, bring back {{FairAffinityFunction}}.
> This is also discussed on dev list: http://apache-ignite-developers.2346864.n4.nabble.com/Resurrect-FairAffinityFunction-td19987.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)