ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kcheng.mvp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1481) It is possible to configure local cache with affinity function
Date Wed, 03 Feb 2016 02:57:39 GMT

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

kcheng.mvp commented on IGNITE-1481:
------------------------------------

Ken,

cache configuration validation and initialization occurs in
GridCacheProcessor class (methods validate() and initialize()).

>From my point of view two changes should be made:

- during cache intialization LocalAffinityFunction should be set to cache
configuration if cache mode is LOCAL;
- warning about ignoring affinity function parameter should be moved from
validate() method to intialize() method.

I hope this will help you.

> It is possible to configure local cache with affinity function
> --------------------------------------------------------------
>
>                 Key: IGNITE-1481
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1481
>             Project: Ignite
>          Issue Type: Bug
>          Components: newbie
>            Reporter: Andrey Gura
>            Assignee: kcheng.mvp
>
> {{LOCAL}} cache always uses {{GridCacheProcessor.LocalAffinityFunction}}.
> Durign configuration of local cache it is possible to pass other affinity function to
cache configuration. All cache operations will work correctly, but user can obtain affinity
manager that internally uses incorrect affinity function ({{GridCacheContext.cctx.affinity().aff.aff}}).
> Expected behaviour: {{GridCacheContext.cctx.affinity().aff.aff}} always refers to {{GridCacheProcessor.LocalAffinityFunction}}
for {{LOCAL}} caches.



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

Mime
View raw message