kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@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
Date Mon, 04 Jun 2012 00:10:23 GMT

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

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

We know that we want to change the ZK layout from the current "1 path per partition" design
to the "1 path per topic" one. This can be done either before we move to the controller implementation
or after. Doing this as part of the controller implementation may make it too big.

I was thinking that n this patch, we just move the ZK layout to 1 path per topic without the
controller logic in place. We will need to (1) patch the create/delete/list topic ddl; (2)
change the topic listener in both KafkaZookeeper and ZookeeperConsumerConnector to read from
the new path. This makes it easier when we move to the controller implementation since the
correct ZK layout is already in place. If we change the ZK layout later, we will need to first
implement the controller logic based on the current ZK layout and change it again later.
                
> 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
>
> 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

        

Mime
View raw message