Do you mind providing a concrete example of the "evidence that's pointing towards the opposite direction" just to make sure we are on the same page on the topic.
On a side note, the latest document describing consistency guarantees is here: https://github.com/apache/zookeeper/blob/master/zookeeper-docs/src/main/resources/markdown/zookeeperInternals.md#sc_consistency . Does this answer some of your questions? On Thu, Aug 27, 2020 at 10:51 AM tison <[email protected]> wrote: > Hi Stanislav, > > The question you raise is a user question so I forward to user mailing > list. Please continue discussion here. > > The first thing I'd like to know in order to understand your question is > that what is "data changes" in your mind? > > ZooKeeper uses watcher mechanism to reflect to data changes, which is > designed possibly miss some changes. > > Best, > tison. > > > Stanislav Kozlovski <[email protected]> 于2020年8月28日周五 上午1:26写道： > > > Hello! > > > > We were investigating an issue with consistent reads in ZK which made us > > question our assumptions. > > We believe that ZK offers sequential consistency such that if a client > > creates a node with zxid 0x110000122a, it should be able to see (read) > all > > data changes at least up to that zxid. > > > > Could I ask if this is a correct understanding? We seem to be seeing > > evidence that's pointing towards the opposite direction. > > > > Looking at the documentation > > < > > > https://zookeeper.apache.org/doc/r3.1.2/zookeeperProgrammers.html#ch_zkGuarantees > > >, > > it does not seem to address this specific point. It says that "Updates > from > > a client will be applied in the order that they were sent" and talks > about > > "Consistent Cross-Client Views" but does not seem to address cross-client > > update order, unless I'm missing something. > > > > -- > > Best, > > Stanislav > > >
