ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Humphrey Lopez <hmmlo...@gmail.com>
Subject Re: Ignite 2.0: CacheWriteSynchronizationMode = FULL_ASYNC when using cache.putAsync
Date Tue, 16 May 2017 04:51:55 GMT
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:hmmlopez@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.
> 

Mime
View raw message