Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Tue, 19 Apr 2016 23:00:28 +0000 (UTC)
From: "Ismael Juma (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12934528.1453917073000.272715.1461106828719@Atlassian.JIRA>
In-Reply-To: <JIRA.12934528.1453917073000@Atlassian.JIRA>
References: <JIRA.12934528.1453917073000@Atlassian.JIRA>
 <JIRA.12934528.1453917073203@arcas>
Subject: [jira] [Commented] (KAFKA-3158) ConsumerGroupCommand should tell
 whether group is actually dead
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ismael Juma commented on KAFKA-3158:
------------------------------------

[~imandhan], no-one is working on this JIRA. Would you like to pick it up?

> 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
>            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)