Hi Folks,

WriteSynchronizationMode allows users to pick from 3 different
synchronization modes (FULL_SYNC, FULL_ASYNC, PRIMARY_SYNC) when performing
writes on a distributed setting.

Based on my understanding, when writing to the cache (whether inside or
outside of a transaction) the user-perceived latency must be the same in the
following two scenarios if the WriteSynchronizationMode is set to
PRIMARY_SYNC:

1)one-node cluster where only 1 primary copy of the data exits in a remote
server.
2) two-node cluster where 1 primary copy of the data resides on the remote
server and a backup copy 
    exists in the adjacent server.

In other words, the write latency should not be affected by the number of
backup copies in PRIMARY_SYNC.

However, in my current experiments (performing 2 writes inside a
transaction), I am facing different latencies for the above settings (3RTT
for scenario #1 and 4RTT for scenario #2 ). 

Can someone please explain why this is happening how I can fix it? 



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

Reply via email to