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] [Updated] (KAFKA-336) add an admin RPC to communicate state changes between the controller and the broker
Date Wed, 06 Jun 2012 01:32:22 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jun Rao updated KAFKA-336:
--------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Fixed as part of kafka-349
                
> add an admin RPC to communicate state changes between the controller and the broker
> -----------------------------------------------------------------------------------
>
>                 Key: KAFKA-336
>                 URL: https://issues.apache.org/jira/browse/KAFKA-336
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Jun Rao
>            Assignee: Yang Ye
>             Fix For: 0.8
>
>         Attachments: controller_broker_RPC.patch, rpc-v3.patch, rpc.patch.v2
>
>   Original Estimate: 252h
>  Remaining Estimate: 252h
>
> Based on the discussion in https://cwiki.apache.org/confluence/display/KAFKA/kafka+Detailed+Replication+Design+V3
, it's more efficient to communicate state change commands between the controller and the
broker using a direct RPC than via ZK. This ticket will be implementing an admin RPC client
for the controller to send state change commands.

--
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