You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/05/28 23:08:13 UTC

[jira] [Resolved] (KAFKA-3158) ConsumerGroupCommand should tell whether group is actually dead

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

Ismael Juma resolved KAFKA-3158.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.1.0

Issue resolved by pull request 1429
[https://github.com/apache/kafka/pull/1429]

> 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
>             Fix For: 0.10.1.0
>
>
> 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)