+ The C* coordinator send async write requests to the replicas.
This is very important since it allows it to return a low latency
reply to the client once the CL is reached. You wouldn't want
to serialize the replicas one after the other.
+ The client <-> server sync/async isn't related to the coordinator
in this case.
+ In the case of concurrent writes (always the case...), the time stamp
sets the order. Note that it's possible to work with client timestamps
or
server timestamps. The client ones are usually the best choice.
Note that C* each node can be a coordinator (one per request) and its
the desired case in order to load balance the incoming requests. Once again,
timestamps determine the order among the requests.
Cheers,
Dor
On Mon, Feb 20, 2017 at 4:12 PM, Kant Kodali <k...@peernova.com> wrote:
> Hi,
>
> when C* coordinator writes to replicas does it write it in same order or
> different order? other words, Does the replication happen synchronously or
> asynchrnoulsy ? Also does this depend sync or async client? What happens in
> the case of concurrent writes to a coordinator ?
>
> Thanks,
> kant
>
