Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/215
The watcher code is counting on starting the ZooKeeper operation from the
same thread as the Watcher. You're right the connection issues can get in the
way of this. But, to me, this is all moot. This is how Curator works today and
it would be very disruptive to change it now. We can't change deep behavior
like this without it affecting users of the library.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
