You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2017/01/18 01:51:27 UTC
[jira] [Comment Edited] (ZOOKEEPER-2139) Support multiple ZooKeeper
client, with different configurations, in a single JVM
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827233#comment-15827233 ]
Rakesh R edited comment on ZOOKEEPER-2139 at 1/18/17 1:50 AM:
--------------------------------------------------------------
bq. I just found that the bug exists in our patch but not in the original attached to this issue. It looks like there was a mistake while applying the patch.
[~haridsv], do you meant ZOOKEEPER-2667 is not a problem. If so, shall we close this?
was (Author: rakeshr):
bq. I just found that the bug exists in our patch but not in the original attached to this issue. It looks like there was a mistake while applying the patch.
Do you meant ZOOKEEPER-2667 is an invalid issue. If so, shall we close this?
> Support multiple ZooKeeper client, with different configurations, in a single JVM
> ---------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2139
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client
> Affects Versions: 3.5.0
> Reporter: Surendra Singh Lilhore
> Assignee: Arshad Mohammad
> Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2139-05.patch, ZOOKEEPER-2139-06.patch, ZOOKEEPER-2139-07.patch, ZOOKEEPER-2139-08.patch, ZOOKEEPER-2139-09.patch, ZOOKEEPER-2139-10.patch, ZOOKEEPER-2139-11.patch, ZOOKEEPER-2139-12.patch, ZOOKEEPER-2139-13.patch, ZOOKEEPER-2139-14.patch, ZOOKEEPER-2139_1.patch, ZOOKEEPER-2139_2.patch, ZOOKEEPER-2139.patch, ZOOKEEPER-2139.patch
>
>
> I have two ZK client in one JVM, one is secure client and second is normal client (For non secure cluster).
> "zookeeper.sasl.client" system property is "true" by default, because of this my second client connection is failing.
> We should pass all client configurations in client constructor like HDFS client.
> For example :
> {code}
> public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher, Configuration conf) throws IOException
> {
> ......
> ......
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)