You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2017/07/10 08:42:00 UTC

[jira] [Commented] (IGNITE-5446) Always use late affinity assignment mode

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

Semen Boikov commented on IGNITE-5446:
--------------------------------------

For 2.1 just made IgniteConfiguration.setLateAffinityAssignment deprecated and no-op, so late affinity mode is always used. However do need cleanup of internal code.

> Always use late affinity assignment mode
> ----------------------------------------
>
>                 Key: IGNITE-5446
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5446
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Semen Boikov
>            Assignee: Semen Boikov
>             Fix For: 2.2
>
>
> In Igntie there are two modes for cache affinity changing (IgniteConfiguration.isLateAffinityAssignment=true/false). Late affinity assignment mode is enabled by default and there is no case when it can be useful to disable it. Need deprecate property IgniteConfiguration.isLateAffinityAssignment and always user late affinit assignment mode.



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