You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/07/10 08:24:00 UTC

[jira] [Updated] (IGNITE-4786) Try get rid of exchange futures history and affinity history

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

Vladimir Ozerov updated IGNITE-4786:
------------------------------------
    Fix Version/s:     (was: 2.1)
                   2.2

> Try get rid of exchange futures history and affinity history
> ------------------------------------------------------------
>
>                 Key: IGNITE-4786
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4786
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Igor Seliverstov
>            Priority: Critical
>             Fix For: 2.2
>
>
> Currently ignite stores calculated affinity history (GridAffinityAssignmentCache) and finished exchange futures (GridCachePartitionExchangeManager). If requested history data is not available this causes runtime exception and unpredictable consequences.
> Ideally we need get rid of history and if some operation requires old affinity data then operation should retry on current topology version, or operation handling should be changed so that affinity data is not needed to finish operation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)