ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-5836) AffinityFunctionContext should provide consistent previous assignment
Date Thu, 27 Sep 2018 09:06:00 GMT

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

Vladimir Ozerov commented on IGNITE-5836:

Moved to 2.8 due to inactivity. Please feel free to move back if you will be able to complete
the ticket by AI 2.7 code freeze date, September 30, 2018.

> 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
>            Assignee: Evgenii Zhuravlev
>            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
> 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

View raw message