Hi, Replicated cache has backups amount that equal to cluster nodes amount minus one because this one is primary. Amount of nodes in cluster can be changed during time so we use Integer.MAX_VALUE magic number for backups in case of replicated cache. Amount of backups doesn't depend on cache memory mode and you should not specify what node is primary and what is backup. It is affinity function responsibility. If you will set backups parameter to zero (or any other value) for replicated cache it will be ignored.
In fact, partitioned and replicated caches are implemented in the same way. But there are some implementation details because our focus is high performance. On Tue, Nov 15, 2016 at 1:43 AM, styriver <scott_tyri...@mgic.com> wrote: > Hello I am dumping the cache configuration for my defined caches. I am > seeing > this as the backup number > memMode=OFFHEAP_TIERED cacheMode=REPLICATED, atomicityMode=TRANSACTIONAL, > atomicWriteOrderMode=null, backups=2147483647 > > I am not setting the backups property in any of my configurations so this > must be the default. This is the same number for both the OFFHEAP_TIERED > and > ONHEAP_TIERED. We have two server nodes and am not specifying any of the > nodes as primary or backup. Wondering what the implications of having this > number set to this value. Is it only applicable if the cacheMode is > PARTIONED? Like to know if I should set this to zero or not? > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Question-about-backups-tp8968.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
