Hello!
Unfortunately if you have clients coming and parting from cluster all the
time, your rebalance can take long time.
There is a ticket on this issue:
https://issues.apache.org/jira/browse/IGNITE-7165
It looks like it will be fixed in 2.7.
Regards,
--
Ilya Kasnacheev
вт, 13 нояб. 2018 г.
Has any one got anything to say on this.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Add to above
I also see below, completed rebalancing and cancelled rebalancing logs after
any client joins connects to the cluster. Is it normal behavior of re
balance
[2018-11-08T20:06:36,936][INFO
][disco-event-worker-#341%EDIFCustomer%][GridDiscoveryManager] ^-- Node
[id=B5C2D0EE-72CB-49A6-
Hi
We are using Ignite 2.6
I have used rebalanceThreadPool to 16 and rebalanceBatchSize to 2 MB and we
have total data around 12 TB with 6 nodes cluster.
We are using very high end machines which are 128 CPU and 2 TB RAM etc, we
are finding ways to get re-balancing to be completed fast, right no