Fournier, Camille F.: > Did anyone ever check resetting watches at client reconnect on a client > with a chroot? Looking at the code, we store the watches associated with > the non-chroot path, but they are set by the original request prepending > chroot to the request. However, it looks like the SetWatches request on > reconnect just calls get on the various watch lists from ZooKeeper, which > don't have the prepended chroot. > > I haven't written a test but I would bet dollars to donuts this is the > problem. > > C seems to be this: ZOOKEEPER-961, ZOOKEEPER-1091
Regards, Thomas Koch, http://www.koch.ro
