[
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arshad Mohammad updated ZOOKEEPER-2139:
---------------------------------------
Attachment: ZOOKEEPER-2139-06.patch
Submitting improved version of the previous patch. Now all the client side
properties can be ZooKeeper instance specific.
Created {{org.apache.zookeeper.common.Configuration}} which contains
information of the properties which are common between client and server
{{org.apache.zookeeper.client.ClientConfiguration}} contains properties info
which are specific to client
Still some scenarios are left for testing,Will submit complete test scenario
soon.
Submitting the patch early to take CI feedback as well as get it reviewed
early.
> 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: Arshad Mohammad
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2139-05.patch, ZOOKEEPER-2139-06.patch,
> ZOOKEEPER-2139.patch, ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch,
> ZOOKEEPER-2139_2.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)
