[
https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashanth Menon updated KAFKA-329:
----------------------------------
Attachment: KAFKA-329-DRAFT.patch
Hi all,
I've attached a very early draft of the work required here. It changes the
CreateTopic ddl, currently writing to both old and new locations to keep tests
running while the patch is completed. The largest change comes in
KafkaZooKeeper to the topic watcher. Thinking about it, most of the code in
there regarding leader election will be gone when the controller goes in, but
I've left the important pieces in there to keep tests working. I'll continue
working to get the consumer ZooKeeperConsumerConnector side working with the
new path.
I'd like to get some preliminary feedback on the patch. Hopefully, I'm going
in the right direction based off my understanding on the V3 design. Comments
welcome :)
> 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
> Assignee: Prashanth Menon
> Labels: replication
> Attachments: KAFKA-329-DRAFT.patch
>
>
> 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
