eolivelli commented on issue #4253: URL: https://github.com/apache/bookkeeper/issues/4253#issuecomment-2027049371
I think that we should not put any requirements about this point. In a distributed environment many sequences of events may "happen" and it is not guaranteed (for ZK for also for many other systems, due to the intrinsic nature of distributed systems) that you observe all the events, the only real guarantee is that eventually the local node is notified and it is able to build a local consistent view of the metadata. I don't think it is a problem if the callback is called even if nothing changed, it is more like a feature. Think about this case: - state A - client connects and sets a watch - client disconnects - state B - state changes to C - state changes to B - client reconnects - the client is notified that "something happened" and then it can see that the current state is B The client never sees that the "state" changed from B to C and then back to B, but it is important that it is notified that the state changed and it is now B (and not A) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
