Details
-
Improvement
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
3.5.0
-
None
Description
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 :
public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher, Configuration conf) throws IOException { ...... ...... }
Attachments
Attachments
Issue Links
- breaks
-
ZOOKEEPER-2667 NPE in the patch for ZOOKEEPER-2139 when multiple connections are made
- Resolved
-
ZOOKEEPER-2517 jute.maxbuffer is ignored
- Closed
- contains
-
ZOOKEEPER-2396 Login object in ZooKeeperSaslClient is static
- Closed
- duplicates
-
ZOOKEEPER-2103 ZooKeeper Client Configuration
- Resolved
-
ZOOKEEPER-2331 Many instances of ZookeeperSaslClient in one process - every instance should use different jaas config section.
- Resolved
- is depended upon by
-
KNOX-1133 Update ZooKeeper URLManager implementations to use registry client service
- Open
- is duplicated by
-
ZOOKEEPER-2451 do not make use of system properties for security configuration
- Resolved
- is related to
-
HBASE-14775 Replication can't authenticate with peer Zookeeper with different server principal
- Open
-
ZOOKEEPER-4875 Support pre-constructed ZKConfig in server side
- Open
- relates to
-
ZOOKEEPER-2323 ZooKeeper client enters into infinite AuthFailedException cycle if its unable to recreate Kerberos ticket
- Resolved
-
ZOOKEEPER-2416 Remove Java System property usage from ZooKeeper server code
- Open
-
ZOOKEEPER-3593 fix the default value of jute.maxbuffer in client side and an optimization for the documentation
- Resolved
-
ZOOKEEPER-1467 Make server principal configurable at client side.
- Closed