zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From 邢迪侃 <xingdk.a...@gmail.com>
Subject What is the order of read watch and write completion?
Date Fri, 06 May 2011 03:47:29 GMT
Hi, All,

I'm not sure whether the response (from the client perspective, the
completion callback or the return of a sync call) to a success write
(create, delete, etc) is also queued in the right place among read
completion and read watch.

In detail, for example the current view is:
/a: oldA
/b: oldB

And from the perspective of the zk server, it handles the following two
change in the shown order:
a) /a changes to newA
b) /b changes to newB

I understand, if Tom sets the read watch previously, before reading out the
new content of "/b", Tom will get watch notification of "/a".
My question is if Tom is not reading, but writing. It is Tom that changes
the content of /b. Then is there guarantee that the watch notification of
"/a" will preceed the completion callback (if Tom asetData()) and the return
of setData?

In other words, will the server queue the response to the client's write
request only after previous writes are locally played and triggered watches
are handled and queued into TCP sending tunnel?
Or say, is a success response to a write request a part of a consistent view
for a client?

XING Dikan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message