[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zili Chen resolved ZOOKEEPER-838.
---------------------------------
    Fix Version/s: 3.10.0
       Resolution: Fixed

master via f42c01de73867ffbc12707b3e9f9cd7f847fe462

> Chroot is an attribute of ClientCnxn
> ------------------------------------
>
>                 Key: ZOOKEEPER-838
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-838
>             Project: ZooKeeper
>          Issue Type: Sub-task
>            Reporter: Patrick Datko
>            Assignee: Kezhu Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.10.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to