then may ask you what is difference between https://apacheignite.readme.io/docs/primary-and-backup-copies#section-synchronous-and-asynchronous-backups this and rebalance mode
thanks, slava.koptilin wrote > Hello, > > I think rebalancing makes sense for all types of caches. It does not > matter > what type of cache you use. > Long story short, a replicated cache is a partitioned cache with the > number > of backups equals to the number of nodes minus 1. > > Let's assume that you ingested all data in the cluster, and after that, > added a new node. > In that case, data will be transferred/copied to a new node during > rebalancing. > > Perhaps, EVT_CACHE_REBALANCE_STARTED and EVT_CACHE_REBALANCE_STOPPED will > be useful to track rebalancing. > > Thanks, > Slava. > > вс, 8 июл. 2018 г. в 15:47, Amir Akhmedov < > amir.akhmedov@ > >: > >> Rebalancing is a process when a node joins or leaves (in case backup is >> turned on) a cluster, data will be rebalanced within a cluster to make a >> fair distribution. It's applicable only for partitioned caches. But you >> have replicated cache and it's out of your case. >> >> Thanks, >> Amir >> >> On Jul 8, 2018 4:02 AM, "monstereo" < > mehmetozanguven@ > > wrote: >> >> thank you for your comment, >> I also found that there is a data rebalance in ignite. >> What do you think about this? Which one should I use? >> >> Here is the data rebalance link here >> <https://apacheignite.readme.io/docs/rebalancing> >> >> For SYNCH mode in rebalance says that ::: >> >> "Synchronous rebalancing mode. Distributed caches will not start until >> all >> necessary data is loaded from other available grid nodes. This means that >> any call to cache public API will be blocked until rebalancing is >> finished." >> >> >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >> >> -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
