[
https://issues.apache.org/jira/browse/KAFKA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393650#comment-13393650
]
Prashanth Menon commented on KAFKA-329:
---------------------------------------
Hi Jun,
31, 32, 33, 34 - All Done. I've committed the changes to 0.8.
As for the transient failure, I'm not able to reproduce them, but I suspect it
may have something to do with the timing of topic creation and leader election.
The tests in ZooKeeperConsumerConnectorTest use auto-creation of topics, and
so, the DefaultEventHandler may attempt send messages three times (by default)
and fail before the leader is able to bootstrap itself. If this is indeed the
case, we can either increase the producer retry count or, more
deterministically, create and wait for the leader using the normal
CreateTopicCommand.createTopic and TestUtils.waitUntilLeaderIsElected methods
(which I'd prefer).
> 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
> Fix For: 0.8
>
> Attachments: KAFKA-329-DRAFT-v2.patch, KAFKA-329-DRAFT.patch,
> KAFKA-329-v1.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
