[
https://issues.apache.org/jira/browse/IGNITE-12705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040867#comment-17040867
]
Maxim Muzafarov commented on IGNITE-12705:
------------------------------------------
Hello, I think there is no need to add new {{CacheRebalanceOrder}} since the
rebalanceOrder will be deprecated soon and completely removed.
Can we deprecate and completely remove the relanaceOrder property in this PR? I
think it will simplify everything.
See:
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Deprecation-of-obsolete-rebalancing-functionality-td45824.html
> Schedule rebalancing of SYNC caches with high priority
> ------------------------------------------------------
>
> Key: IGNITE-12705
> URL: https://issues.apache.org/jira/browse/IGNITE-12705
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.8
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In current implementation order in which rebalancing is triggered seems to be
> arbitrary, regardless of the configured rebalanceMode. In this case
> Ignition.start() method is forced to wait not only for rebalancing of SYNC
> caches, but also the ones that are scheduled for rebalancing before it.
> This behavior should be fixed by making SYNC caches rebalance first, before
> going to any other caches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
