Stanislav, A ZK client should only ever see state move forward in terms of ZXID.
This is true even if a client disconnects and reconnects. If you have multiple connections to a ZK cluster, each connection will satisfy this constraint with respect to itself, but one could be behind the other. Sync can be used to force a stricter relationship. On Tue, Sep 1, 2020 at 7:35 AM Stanislav Kozlovski <stanis...@confluent.io> wrote: > ... > > ``` > t1: A creates /myPathA v0 (0x11000012207) > t2: A setData /myPathA v1 (0x11000012208) > t3: B creates /myPathB v0 (0x11000012209) > t4: C reads /myPathB > t5: C reads /myPathA > ``` > > Given that, at t4, C read 0x11000012209, do we have a guarantee that at t5 > C read v1 of /myPathA (0x11000012208)? > Is it possible that it could read v0 (0x11000012207) under some edge > conditions? > >
