[
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370745#comment-14370745
]
Rakesh R commented on ZOOKEEPER-2139:
-------------------------------------
*Adding one more use case:*
Consider a case where my application needs to talk to multiple ZooKeeper
clusters whose principals are different. Here the zookeeper client should have
the intelligence(configuration details) to connect to two different clusters.
I think, with the proposed solution {{ZooKeeper(String connectString, int
sessionTimeout, Watcher watcher, Configuration conf)}}, the ZooKeeper client
can accept the respective configuration through the constructor and instantiate
it using the passed configuration values.
> Zookeeper client configuration should not be java system property
> -----------------------------------------------------------------
>
> 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: surendra singh lilhore
>
> 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)
