[jira] [Commented] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

["Cyrus Vafadari (JIRA)" <ji...@apache.org>]

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

Cyrus Vafadari commented on KAFKA-6788:
---------------------------------------

[~guozhang] I abandoned it a while ago when it didn't get attention, so haven't actively worked on it in a while. I think if the code is moving towards using futures/promise it might be better to start from scratch. If you like this strategy though I'll fix merge conflicts and reopen the PR

> Grouping consumer requests per consumer coordinator in admin client
> -------------------------------------------------------------------
>
>                 Key: KAFKA-6788
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6788
>             Project: Kafka
>          Issue Type: Improvement
>          Components: admin
>            Reporter: Guozhang Wang
>            Assignee: Yishun Guan
>            Priority: Major
>              Labels: newbie++
>
> In KafkaAdminClient, for some requests like describeGroup and deleteGroup, we will first try to get the coordinator for each requested group id, and then send the corresponding request for that group id. However, different group ids could be hosted on the same coordinator, and these requests do support multi group ids be sent within the same request. So we can consider optimize it by grouping the requests per coordinator destination.



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