You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2016/02/29 13:10:18 UTC

[jira] [Updated] (IGNITE-2733) Ignite should use actual AffinityTopologyVersion for LOCAL cache

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

Artem Shutak updated IGNITE-2733:
---------------------------------
    Priority: Minor  (was: Major)

> Ignite should use actual AffinityTopologyVersion for LOCAL cache
> ----------------------------------------------------------------
>
>                 Key: IGNITE-2733
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2733
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Artem Shutak
>            Priority: Minor
>
> The issue created to properly fix IGNITE-2554. Also, current behavior can has another issues with dynamically started LOCAL cache.
> Ignite does not store an affinity assignment history for local cache and always operate with {{AffinityTopologyVersion(1)}}. When cache starts dynamically, an information about dynamically started cache is available only for {{AffinityTopologyVersion(1, 1)}}, but Ignite does not store it. Proper fix should be:
> #* There is no need to store all history for local cache (as Ignite do it now). So, we need just update the head topology version (see GridAffinityAssignmentCache.head field)
> #* We must return right topology version at all project. See, for example, {{GridCacheAffinityManager}} and the following code
> {code}
>         if (cctx.isLocal())
>             topVer = new AffinityTopologyVersion(1);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)