Hi, The only difference between replicated and partitioned caches is that the former has a primary node (as any partitioned cache) for a key while all the other nodes are treated as backups.
An affinity function knows that difference but use the same logic to map a key to a partition and the partition to a primary and then to backups. You can get info from that section: https://apacheignite.readme.io/v2.0/docs/affinity-collocation#section-affinity-function Hope this makes things vivid for you. -- Denis On Mon, May 15, 2017 at 10:16 PM, Gordon Reid (Nine Mile) < gordon.r...@ninemilefinancial.com> wrote: > Thanks Humphrey, yes I have read that. But it is still not clear to me how > the primary node for a key is assigned in a REPLICTED cache, where we have > no specific key affinity specified. > > > > *From:* Humphrey Lopez [mailto:hmmlo...@gmail.com] > *Sent:* Tuesday, 16 May 2017 2:52 PM > *To:* user@ignite.apache.org > *Subject:* Re: Ignite 2.0: CacheWriteSynchronizationMode = FULL_ASYNC > when using cache.putAsync > > > > https://apacheignite.readme.io/v2.0/docs/primary-and- > backup-copies#synchronous-and-asynchronous-backups > > Humphrey > > > On 16 May 2017, at 03:14, Gordon Reid (Nine Mile) <gordon.reid@ > ninemilefinancial.com> wrote: > > Thanks Humphrey. And in the case of PRIMARY_SYNC, how is the primary node > determined for the entity? Will it be the node where the entity was > created? (we are in REPLICATED) > > Thanks,. > > -----Original Message----- > From: Humphrey [mailto:hmmlo...@gmail.com <hmmlo...@gmail.com>] > Sent: Monday, 15 May 2017 5:19 PM > To: user@ignite.apache.org > Subject: Re: Ignite 2.0: CacheWriteSynchronizationMode = FULL_ASYNC when > using cache.putAsync > > Hi Gordon, > > FULL_ASYNC: Do not wait for any server node to acknowledge > > So it will fire and forget, and will not wait for all nodes in cluster to > be updated. That will happen in the background. > > Humphrey > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Ignite-2-0-CacheWriteSynchronizationMode- > FULL-ASYNC-when-using-cache-putAsync-tp12837p12839.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > > > > > > This email and any attachments are proprietary & confidential and are > intended solely for the use of the individuals to whom it is addressed. Any > views or opinions expressed are solely for those of the author and do not > necessarily reflect those of Nine Mile Financial Pty. Limited. If you have > received this email in error, please let us know immediately by reply email > and delete from your system. Nine Mile Financial Pty. Limited. ABN: 346 > 1349 0252 >
