Cross-posting to dev. Guys,
Is there any reason for such implementation? Does it ever makes sense to trigger rebalancing on only one node? I think rebalance() method should broadcast automatically and do the job on all nodes. Just in case, we can also add localRebalance() method. This will be more intuitive and also more consistent with other APIs, like loadCache/localLoadCache. -Val On Wed, Mar 22, 2017 at 11:52 PM, ght230 <ght...@163.com> wrote: > Thank you for your guidance. > > I will try calling IgniteCache.rebalance() via compute broadcast task. > > But I think it is more convenient to start rebalancing manually from > management console, is it right? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Can-I-let-Ignite-to-do-rebalance-at-a- > particular-time-tp11301p11381.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
