You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by 18624049226 <18...@163.com> on 2020/05/03 02:35:20 UTC

About Rebalance Mode (SYNC & NONE)

Hi Community,

For partition mode cache(without persistence enabled),If rebalanceMode 
is configured as NONE, rebalancing will actually occur when a new node 
is added,This does not match the function definition,i think this is a bug.

But,for persistent cache, rebalancing is controlled by the baseline 
topology,For disabling persistent cache, it seems that rebalanceMode 
config to (SYNC & NONE) has no practical significance, so what is the 
value of this parameter design? Is this a legacy of history that is 
about to be abandoned?


Re: About Rebalance Mode (SYNC & NONE)

Posted by Alexei Scherbakov <al...@gmail.com>.
Hi.

You are correct, NONE is a legacy mode and should be removed [1]

Note the baseline can be used with in-memory caches as well. To make it
working you have to disable baseline auto-adjust or set non-zero
auto-adjust timeout.
This will prevent unnecessary rebalancing.

[1] https://issues.apache.org/jira/browse/IGNITE-11417

вс, 3 мая 2020 г. в 05:35, 18624049226 <18...@163.com>:

> Hi Community,
>
> For partition mode cache(without persistence enabled),If rebalanceMode
> is configured as NONE, rebalancing will actually occur when a new node
> is added,This does not match the function definition,i think this is a bug.
>
> But,for persistent cache, rebalancing is controlled by the baseline
> topology,For disabling persistent cache, it seems that rebalanceMode
> config to (SYNC & NONE) has no practical significance, so what is the
> value of this parameter design? Is this a legacy of history that is
> about to be abandoned?
>
>

-- 

Best regards,
Alexei Scherbakov