[
https://issues.apache.org/jira/browse/KAFKA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281737#comment-13281737
]
Jun Rao commented on KAFKA-336:
-------------------------------
Another comment:
14. To facilitate a controller to send commands to individual brokers, it would
useful to have some kind of ControllerCommandManager that has the following API:
ControllerCommandManager {
sendCommand(commandRequest: Request, brokerId: Int)
}
Under the cover, the ControllerCommandManager can potentially maintain a queue
per broker and have a separate send thread that gets command from the queue,
sends the request using a BlockingChannel to the right broker and deserializes
and checks the response.
> 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.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
