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

Jun Rao commented on KAFKA-329:
-------------------------------

The ticket is to revisit topic creation based on the V3 design 
(https://cwiki.apache.org/confluence/display/KAFKA/kafka+Detailed+Replication+Design+V3).
 We probably should first change the ZK layout by using 1 ZK node per topic, 
instead of 1 ZK node per partition. This will make it easier to register 
watches for new topics. Then, when the controller framework is ready, we can 
move the logic of handling new topics to the controller.
                
> Remove the watches/broker for new topics and partitions and change create 
> topic admin API to send start replica state change to all brokers
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-329
>                 URL: https://issues.apache.org/jira/browse/KAFKA-329
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>              Labels: replication
>
> Currently in 0.8, all brokers register a watch on /brokers/topics and 
> /brokers/topics/[topic] for all topics in a Kafka cluster. The watches are 
> required to discover new topics. 
> There is another way this can be achieved, as proposed here - 
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+detailed+design+V2#KafkareplicationdetaileddesignV2-Createtopic
> Basically, the create-topic admin command sends start-replica state change 
> request to all brokers in the assigned replicas list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to