[
https://issues.apache.org/jira/browse/KAFKA-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16544540#comment-16544540
]
Christian Tramnitz commented on KAFKA-7090:
-------------------------------------------
Wouldn't it make sense to have the required configuration *before* the
dependeny is changed to 3.5?
Having said that, I think this request is independent of the Kafka dependency
(you can already run Kafka with ZK 3.5) and there are other, non ZK3.5 and/or
TLS/SSL related Zookeeper configuration directives where it would make sense to
store them in the server.properties rather than in environment.
What would be wrong with passing any zookeeper.* configuration directive to
Zookeeper library?
> 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)
