[
https://issues.apache.org/jira/browse/KAFKA-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yishun Guan updated KAFKA-7146:
-------------------------------
Description:
Subtask of KAFKA-6788. Group consumer requests for describeConsumerGroups().
According to KAFKA-6788:
"
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.
"
was:Subtask of KAFKA-6788. Group consumer requests for
describeConsumerGroups().
> Grouping consumer requests per consumer coordinator in admin client in
> describeConsumerGroups
> ---------------------------------------------------------------------------------------------
>
> Key: KAFKA-7146
> URL: https://issues.apache.org/jira/browse/KAFKA-7146
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Yishun Guan
> Priority: Critical
>
> Subtask of KAFKA-6788. Group consumer requests for describeConsumerGroups().
>
> According to KAFKA-6788:
>
> "
> 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)
