[
https://issues.apache.org/jira/browse/KAFKA-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526390#comment-16526390
]
Manikumar commented on KAFKA-7090:
----------------------------------
Kafka still uses Zookeeper 3.4 client dependency. Currently Zookeeper 3.5 is in
beta release. We may update the dependency after stable Zookeeper 3.5 release.
We may need to do this change, after Kafka upgrades Zookeeper's dependency to
3.5
Related Issue: KAFKA-3287
> Zookeeper client setting in server-properties
> ---------------------------------------------
>
> Key: KAFKA-7090
> URL: https://issues.apache.org/jira/browse/KAFKA-7090
> Project: Kafka
> Issue Type: New Feature
> Components: config, documentation
> Reporter: Christian Tramnitz
> Priority: Minor
>
> There are several Zookeeper client settings that may be used to connect to ZK.
> Currently, it seems only very few zookeeper.* settings are supported in
> Kafka's server.properties file. Wouldn't it make sense to support all
> zookeeper client settings there or where would that need to go?
> I.e. for using Zookeeper 3.5 with TLS enabled, the following properties are
> required:
> zookeeper.clientCnxnSocket
> zookeeper.client.secure
> zookeeper.ssl.keyStore.location
> zookeeper.ssl.keyStore.password
> zookeeper.ssl.trustStore.location
> zookeeper.ssl.trustStore.password
> It's obviously possible to pass them through "-D", but especially for the
> keystore password, I'd be more comfortable with this sitting in the
> properties file than being visible in the process list...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
