RE: Effect of WriteSynchronizationMode on write operations inside atransaction in Apache Ignite

[Stanislav Lukyanov <st...@gmail.com>]

Hi,

Generally, your initial thoughts on the expected latency are correct – PRIMARY_SYNC allows you not to wait for the writes
to complete on the backups. However, some of the operations still have to be completed on all nodes (e.g. acquiring key locks),
so increasing the number of backups does affect the execution time.

If what you need is a local copy to speed up reads than you’re probably looking for a near cache:
https://apacheignite.readme.io/docs/near-caches

Stan

From: Kia Rahmani
Sent: 13 августа 2018 г. 22:22
To: user@ignite.apache.org
Subject: Re: Effect of WriteSynchronizationMode on write operations inside atransaction in Apache Ignite

The main reason I want to add backups is to allow very fast reads (assuming
backup reads are allowed). 
Do you know of any way of keeping (stale) copies locally (next to the
clients) in order to save network latency in read operations, without
affecting write latency?





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/