Sam, you can control rebalancing with CacheConfiguration.setRebalance***() properties. Take a look and rebalanceDelay, batchsize and prefetch count. You can disable rebalancing by setting negative delay - this way you will have to manually trigger rebalancing from API or Visor.
> 2. PUT will re-balance partitions among multiple cache server node or not? Did not understand this. Cache updates are propagated to all affinity nodes (primary and backups) including those which are currently being loaded. --Yakov 2017-01-19 22:43 GMT+03:00 javastuff....@gmail.com <javastuff....@gmail.com> : > Hi Val, > > I agree ASYNC makes more sense, but need tuning and lighting fast network > to > complete GBs of data. > > If it is just about backups then using NONE re-balancing mode can help in > certain usecases, by avoiding network transfers of GBs of data. > > Side cache - Persistent store is DB, Cache does not have required data then > app will fetch from DB and supply to cache for further fetches. Cache > Partition backup not needed because there is DB backup. > > In this case losing data from cache does not hurt alot with up-down scaling > of cache cluster. > > Question - > 1. NONE mode - shut down of a node will transfer data to other node or not? > 2. PUT will re-balance partitions among multiple cache server node or not? > > Thanks, > -Sam > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Data-Rebalancing-Transactions-tp10092p10146.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
