Hello Igniters,
Each cache group has “rebalance order” property. As javadoc for
getRebalanceOrder() says: “Note that cache with order {@code 0} does not
participate in ordering. This means that cache with rebalance order {@code
0} will never wait for any other caches. All caches with order {@code 0}
will be rebalanced right away concurrently with each other and ordered
rebalance processes. If not set, cache order is 0, i.e. rebalancing is not
ordered.”
In fact GridCachePartitionExchangeManager always build the chain of
rebalancing cache groups to start (even for cache order ZERO):
ignite-sys-cache -> cacheR -> cacheR3 -> cacheR2 -> cacheR5 -> cacheR1.
If one of these groups will fail to start further groups will never be run.
* Question 1*: Should we fix javadoc description or create a bug for fixing
such rebalance behavior?
[1]
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java#L2630
