[
https://issues.apache.org/jira/browse/IGNITE-12705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040970#comment-17040970
]
Vyacheslav Koptilin commented on IGNITE-12705:
----------------------------------------------
Yes, I thought about the approach you mentioned. IMHO, this way of fixing has
the following drawbacks:
- it breaks the existing contract. I mean that the SYNC cache will always take
precedence even though it has a rebalance order greater than the ASYNC cache.
And I admit the fact that someone can use this functionality.
- it seems we cannot guarantee that 'ignite-sys-cache' will be rebalanced in
the first place. For now, it guaranteed by the fact that this cache has
rebalancing order equals to '-2'. By default, the rebalance order is 0.
> 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)
