You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Kosarev (Jira)" <ji...@apache.org> on 2020/02/12 08:49:00 UTC

[jira] [Commented] (IGNITE-12662) Get rid of CacheConfiguration#getRebalanceDelay and related functionality.

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

Sergey Kosarev commented on IGNITE-12662:
-----------------------------------------

[~ascherbakov], I believe it can't be done until in-memory caches will use baseline topology, i.e until [IGNITE-8414|https://issues.apache.org/jira/browse/IGNITE-8414] is implemented. Do you agree?

> Get rid of CacheConfiguration#getRebalanceDelay and related functionality.
> --------------------------------------------------------------------------
>
>                 Key: IGNITE-12662
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12662
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexey Scherbakov
>            Priority: Major
>             Fix For: 2.9
>
>
> We have for a long time this property to mitigate a case with premature rebalancing on node restart.
> Currently this is handled by baseline topology.
> I suggest to deprecate and remove related functionality in next releases.
> For example org.apache.ignite.IgniteCache#rebalance is no longer needed as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)