[
https://issues.apache.org/jira/browse/KAFKA-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230001#comment-14230001
]
Andrii Biletskyi edited comment on KAFKA-1802 at 12/1/14 4:37 PM:
------------------------------------------------------------------
Proposed RQ/RP format:
===
ControllerDiscoveryRequest =>
// Comment: empty request body
ControllerDiscoveryResponse => [Broker] Controller
Controller => Broker
Broker => NodeId Host Port
NodeId => int32
Host => string
Port => int32
// Comment: controller will be included in [Broker] list, for simplicity
===
I'll update "A Guide To The Kafka Protocol" if there will be no major remarks.
was (Author: abiletskyi):
Proposed RQ/RP format:
===
ControllerDiscoveryRequest =>
// Comment: empty response body
ControllerDiscoveryResponse => [Broker] Controller
Controller => Broker
Broker => NodeId Host Port
NodeId => int32
Host => string
Port => int32
// Comment: controller will be included in [Broker] list, for simplicity
===
I'll update "A Guide To The Kafka Protocol" if there will be no major remarks.
> Add a new type of request for the discovery of the controller
> -------------------------------------------------------------
>
> Key: KAFKA-1802
> URL: https://issues.apache.org/jira/browse/KAFKA-1802
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Joe Stein
> Fix For: 0.8.3
>
>
> The goal here is like meta data discovery is for producer so CLI can find
> which broker it should send the rest of its admin requests too. Any broker
> can respond to this specific AdminMeta RQ/RP but only the controller broker
> should be responding to Admin message otherwise that broker should respond to
> any admin message with the response for what the controller is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
