[
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371008#comment-14371008
]
Rakesh R commented on ZOOKEEPER-2139:
-------------------------------------
bq.my application needs to talk to multiple ZooKeeper clusters whose principals
are different.
Presently, this can be achieved by setting specific principal and
zookeeper.sasl.clientconfig to the System property before establish a
connection. I could see there is a room for improving the client side
configurations by passing the {{Configuration}} instead of {{System property}}.
> 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)
