[
https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288278#comment-13288278
]
Prashanth Menon commented on KAFKA-329:
---------------------------------------
So, changing the CreateTopicCommand and AdminUtils to place the topic+replica
assignment into the new ZK path is simple, but I'm not sure changing the ZK
watch structure can be done in this ticket without either breaking several
tests that rely on existing ZK watch behaviour or implementing additional
watchers that will be integrated/used when the controller is implemented. It
may be a better idea to make this a subtask of the controller implementation
ticket and roll it in with the larger controller patch? Or perhaps break up
the controller ticket by the sections outlined in the V3 wiki along with a
common framework?
Let me know if I'm missing something or over complicating things, the V3 design
is a little knew to me so I may have missed some discussions.
> 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
