You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2022/11/15 16:17:00 UTC

[jira] [Resolved] (KAFKA-7206) Enable batching in FindCoordinator

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

Mickael Maison resolved KAFKA-7206.
-----------------------------------
    Fix Version/s: 3.0.0
       Resolution: Duplicate

Duplicate of https://issues.apache.org/jira/browse/KAFKA-12663

 

> 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++
>             Fix For: 3.0.0
>
>
> 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
(v8.20.10#820010)