You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Andrii Biletskyi (JIRA)" <ji...@apache.org> on 2014/12/01 17:37:12 UTC

[jira] [Commented] (KAFKA-1802) Add a new type of request for the discovery of the controller

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

Andrii Biletskyi commented on KAFKA-1802:
-----------------------------------------

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)