[
https://issues.apache.org/jira/browse/KAFKA-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296928#comment-15296928
]
Jason Gustafson commented on KAFKA-3158:
----------------------------------------
[~imandhan] The easiest way to reproduce the problem is to query a group which
you know doesn't exist. If you do so, you'll get the message above that the
group is either doesn't exist or is rebalancing, but we really should be able
to tell the user that the group doesn't exist in this case. If you look in
{{AdminClient.describeConsumerGroup()}}, we return an empty list both when the
group is dead (i.e. has no members) and when it is not stable (i.e.
rebalancing). So the caller has no way to distinguish the cases. Maybe a simple
option to fix this is to include the state in the response of that method?
Either that, or we could return an {{Option}} where {{None}} indicates that the
group doesn't exist?
> ConsumerGroupCommand should tell whether group is actually dead
> ---------------------------------------------------------------
>
> Key: KAFKA-3158
> URL: https://issues.apache.org/jira/browse/KAFKA-3158
> Project: Kafka
> Issue Type: Improvement
> Components: admin, consumer
> Affects Versions: 0.9.0.0
> Reporter: Jason Gustafson
> Assignee: Ishita Mandhan
> Priority: Minor
>
> Currently the consumer group script reports the following when a group is
> dead or rebalancing:
> {code}
> Consumer group `foo` does not exist or is rebalancing.
> {code}
> But it's annoying not to know which is actually the case. Since the group
> state is exposed in the DescribeGroupRequest, we should be able to give
> different messages for each case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
