[jira] [Commented] (KAFKA-6805) Allow dynamic broker configs to be configured in ZooKeeper before starting broker

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-6805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444274#comment-16444274 ] 

ASF GitHub Bot commented on KAFKA-6805:
---------------------------------------

rajinisivaram opened a new pull request #4898: KAFKA-6805: Enable broker configs to be stored in ZK before broker start
URL: https://github.com/apache/kafka/pull/4898
 
 
   Support configuration of dynamic broker configs in ZooKeeper before starting brokers using ConfigCommand. This will allow password configs to be encrypted and stored in ZooKeeper, without requiring clear passwords in server.properties to bootstrap the broker first.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Allow dynamic broker configs to be configured in ZooKeeper before starting broker
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-6805
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6805
>             Project: Kafka
>          Issue Type: Task
>          Components: tools
>            Reporter: Rajini Sivaram
>            Assignee: Rajini Sivaram
>            Priority: Major
>             Fix For: 2.0.0
>
>
> At the moment, dynamic broker configs like SSL keystore and password can be configured using ConfigCommand only after a broker is started (using the new AdminClient). To start a broker, these configs have to be defined in server.properties. We want to restrict updates using ZooKeeper once broker starts up, but we should allow updates using ZK prior to starting brokers. This is particularly useful for password configs which are stored encrypted in ZK, making it difficult to set manually before starting brokers.
> ConfigCommand is being updated to talk to AdminClient under KIP-248, but we will need to maintain the tool using ZK to enable credentials to be created in ZK before starting brokers. So the functionality to set broker configs can sit alongside that.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)