[jira] [Comment Edited] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

["Vahid Hashemian (JIRA)" <ji...@apache.org>]

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

Vahid Hashemian edited comment on KAFKA-3144 at 6/15/16 12:26 AM:
------------------------------------------------------------------

[~junrao] It seems the reason for this is in the new consumer (unlike the old consumer) {{Dead}} groups are permanently removed and so there is no offset information preserved for them. After the last consumer of the group is gone the group is gone too. In fact, there is no difference between a dead group and a group that was never created. To mimic the behavior of old consumer groups we would need to preserve dead groups and distinguish between dead and non-existent groups.


was (Author: vahid):
[~junrao] It seems the reason for this is groups with no members are marked as "Dead" and, as a result, are not processed in ConsumerGroupCommand. The options to change that are (1) keep the groups alive even when their members die. (2) leave them as "Dead" but somehow retrieve their topic partition offsets. I was wondering which option you think is the one to go with? Thanks.

> report members with no assigned partitions in ConsumerGroupCommand
> ------------------------------------------------------------------
>
>                 Key: KAFKA-3144
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3144
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.9.0.0
>            Reporter: Jun Rao
>            Assignee: Vahid Hashemian
>              Labels: newbie
>
> A couple of suggestions on improving ConsumerGroupCommand. 
> 1. It would be useful to list members with no assigned partitions when doing describe in ConsumerGroupCommand.
> 2. Currently, we show the client.id of each member when doing describe in ConsumerGroupCommand. Since client.id is supposed to be the logical application id, all members in the same group are supposed to set the same client.id. So, it would be clearer if we show the client id as well as the member id.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)