[
https://issues.apache.org/jira/browse/KAFKA-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525150#comment-17525150
]
Guozhang Wang commented on KAFKA-13765:
---------------------------------------
Hello [~rleslie] thanks for the careful thoughts. And I agree 100% with you
about the concerns of compatibility breaks.
I think we do not need to extend the {{DescribeConsumerGroupsOptions}} or
{{DescribeConsumerGroupsResult}} since the existing fields are sufficient. What
I had in mind is indeed just on the wrapper tools (like the
kafka-consumer-groups.sh) which, by looking at the
{{DescribeConsumerGroupsResult#state}} to decide which members to print out. Of
course we'd still need a flag in the shell script to indicate "not print
members when state is rebalancing" etc which would still need a KIP.
> Describe-consumer admin should not return unstable membership information
> -------------------------------------------------------------------------
>
> Key: KAFKA-13765
> URL: https://issues.apache.org/jira/browse/KAFKA-13765
> Project: Kafka
> Issue Type: Bug
> Components: admin
> Reporter: Guozhang Wang
> Priority: Major
>
> When a consumer group is in the “prepare-rebalance” phase, it's unclear if
> all its currently registered members would still be re-joining in the new
> generation or not, in this case, if we simply return the current members map
> to the describe-consumer request it may be misleading as users would be
> getting spurious results that may contain those dropping or even zombie
> consumers.
> So I think during the prepare-rebalance phase, we should either only return
> members who's join-group requests have already been received, OR we simply
> return the response with no members and indicate that via prepare-rebalance
> state the membership info is unstable and hence won't be returned.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
