Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
chroot
Description
It would be better to have one process that uses ZooKeeper for different things
(managing a list of work, locking some unrelated locks elsewhere). So there are
components that do this work inside the same process. These components should
get the same zookeeper-client reference chroot'ed for their needs.
So it'd be much better, if the ClientCnxn would not care about the chroot.
Attachments
Issue Links
- is related to
-
ZOOKEEPER-961 Watch recovery after disconnection when connection string contains a prefix
- Closed
-
ZOOKEEPER-4565 Config watch path get truncated abnormally and fail chroot zookeeper client
- Closed
- relates to
-
ZOOKEEPER-4601 Define getConfig Watcher behavior in chroot ZooKeeper
- Resolved
- links to