This is most commonly due, in my own history of programming errors, to writing code that has a race window in it. It is conceivable that cross data-center operation would make such a race more of a problem.
Can you say a bit about your code? Did you make sure to use standard idioms as opposed to setting the watch in a different call from reading the data? On Wed, Jun 1, 2011 at 11:40 AM, Jun Rao <[email protected]> wrote: > Hi, > > I have a setup where multiple ZK clients are sitting in a different > datacenter from the ZK server. All clients registered the same child > watcher > on a path. However, when the children of the path changed, the watcher on 1 > of the clients didn't fire. This seems to have happened a couple of times > to > me. I am using ZK 3.3.3. Has anyone used ZK in a cross datacenter setup and > seen problems like that before? > > Thanks, > > Jun >
