[
https://issues.apache.org/jira/browse/KAFKA-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300692#comment-15300692
]
ASF GitHub Bot commented on KAFKA-3158:
---------------------------------------
GitHub user imandhan opened a pull request:
https://github.com/apache/kafka/pull/1429
KAFKA-3158: ConsumerGroupCommand should tell whether group is actually dead
This patch fix differentiates between when a consumer group is rebalancing
or dead and reports the appropriate error message.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/imandhan/kafka KAFKA-3158
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1429.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1429
----
commit a0c64a404ba7a33cff95684f104c69dffa5d45fb
Author: Ishita Mandhan <iman...@us.ibm.com>
Date: 2016-05-25T19:18:01Z
KAFKA-3158
Differentiates between when a consumer group is rebalancing or dead and
reports the appropriate
error message.
----
> 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)
