Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Date: Tue, 12 Jun 2012 16:58:43 +0000 (UTC)
From: "Jun Rao (JIRA)" <jira@apache.org>
To: kafka-dev@incubator.apache.org
Message-ID: <1871551364.8344.1339520323113.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <8274720.3346.1333990278151.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KAFKA-329) Remove the watches/broker for new
 topics and partitions and change create topic admin API to send start
 replica state change to all brokers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Thanks for draft v2. Some quick comments:

21. KafkaZookeeper: Do we still need onTopicChange and initLeader if we keep handleNewTopics?

22. AdminUtils: We should get rid of the old way of storing topic data in ZK and just keep the new way.

As for json library, any json library works well with Scala?
                
> 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-v2.patch, 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