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

Guozhang Wang commented on KAFKA-7206:
--------------------------------------

[~sagarrao] I think [~shung] has tried to implemented this idea before but it 
turns out to be quite complex (maybe Yishun can give you some pointers of his 
past contributions). If this is your first work in the codebase that maybe very 
ambitious. Anyways, it is up to you and Yishun.

> Enable batching in FindCoordinator
> ----------------------------------
>
>                 Key: KAFKA-7206
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7206
>             Project: Kafka
>          Issue Type: Improvement
>          Components: admin
>            Reporter: Yishun Guan
>            Assignee: Yishun Guan
>            Priority: Critical
>              Labels: needs-discussion, needs-kip, newbie++
>
> To quote [~guozhang] :
> "The proposal is that, we extend FindCoordinatorRequest to have multiple 
> consumer ids: today each FindCoordinatorRequest only contains a single 
> consumer id, so in our scenario we need to send N request for N consumer 
> groups still. If we can request for coordinators in a single request, then 
> the workflow could be simplified to:
>  # send a single FindCoordinatorRequest to a broker asking for coordinators 
> of all consumer groups.
>  1.a) note that the response may still succeed in finding some coordinators 
> while error on others, and we need to handle them on that granularity (see 
> below).
>  # and then for the collected coordinator, group them by coordinator id and 
> send one request per coordinator destination.
> Note that this change would require the version to be bumped up, to 
> FIND_COORDINATOR_REQUEST_V3 for such protocol changes, also the RESPONSE 
> version should be bumped up in order to include multiple coordinators."
> A KIP is needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to