Only lateAffinityAssignment for 2.1

[Semyon Boikov]

Hi all,

Currently in Igntie we have two modes for cache affinity changing
(IgniteConfiguration.isLateAffinityAssignment=true/false). Late affinity
assignment mode is enabled by default and I do not see when it can be
useful to disable it. Does it make sense for 2.1 to deprecate property
IgniteConfiguration.isLateAffinityAssignment and internally always use late
affinity assignment mode? This will allow to simplify cache code (e.g. get
rid of ForceKeyRequests/Responses).

What do you think?

Thanks!

[yzhdanov]

Absolutely agree.

Please make sure that we switch affinity version only when partition N
migrates from current node for all caches. Makes sense?

--Yakov

[Semyon Boikov]

Now affinity version is switched only when migration for new primaries
finishes for all partitions and for all caches.

On Tue, Jun 6, 2017 at 2:01 PM, Yakov Zhdanov <[hidden email]> wrote:

> Absolutely agree.
>
> Please make sure that we switch affinity version only when partition N
> migrates from current node for all caches. Makes sense?
>
> --Yakov
>

[dsetrakyan]

On Tue, Jun 6, 2017 at 4:23 AM, Semyon Boikov <[hidden email]> wrote:

> Now affinity version is switched only when migration for new primaries
> finishes for all partitions and for all caches.
>

Sounds great. Semyon, is there documentation that needs to be updated as
well?

[Semyon Boikov]

Created https://issues.apache.org/jira/browse/IGNITE-5446.

Thanks

On Wed, Jun 7, 2017 at 5:25 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> On Tue, Jun 6, 2017 at 4:23 AM, Semyon Boikov <[hidden email]>
> wrote:
>
> > Now affinity version is switched only when migration for new primaries
> > finishes for all partitions and for all caches.
> >
>
> Sounds great. Semyon, is there documentation that needs to be updated as
> well?
>