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

2016-09-01 Thread Vahid Hashemian (JIRA)

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

Vahid Hashemian edited comment on KAFKA-3144 at 9/1/16 8:56 PM:


[~junrao] How do you think the consumer group coordinator (I assume the broker 
id is sufficient) should be displayed in the output?
One option would be in a new {{COORDINATOR}} column (which repeats the same id 
in each row similar to how group name gets repeated):
{code}
GROUPCOORDINATORTOPIC   PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  
  MEMBER-ID MEMBER-HOST  CLIENT-ID
group1   0  bar0  445 445 0 
 group1_kafka-1472762710305-24f2ffa3
  
{code}



was (Author: vahid):
[~junrao] How do you think the consumer group coordinator (I assume the broker 
id is sufficient) should be displayed in the output?
One option would be in a new {{COORDINATOR}} column (which repeats the same id 
in each row similar to how group name gets repeated):
{code}
GROUPCOORDINATOR  TOPIC PARTITION  CURRENT-OFFSET  
LOG-END-OFFSET  LAGMEMBER-ID MEMBER-HOST 
CLIENT-ID
group1   0bar   0  445 445  
   0  group1_kafka-1472762710305-24f2ffa3   
   
{code}


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


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

2016-09-01 Thread Vahid Hashemian (JIRA)

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

Vahid Hashemian edited comment on KAFKA-3144 at 9/2/16 12:44 AM:
-

[~junrao] How do you think the consumer group coordinator (I assume the broker 
id is sufficient) should be displayed in the output?
One option would be in a new {{COORDINATOR}} column (which repeats the same id 
in each row similar to how group name gets repeated):
{code}
GROUPCOORDINATORTOPIC   PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  
  MEMBER-ID MEMBER-HOST  CLIENT-ID
group1   0  bar0  445 445 0 
 group1_kafka-1472762710305-24f2ffa3
  
{code}

Also, I believe this applies to the case where {{--new-consumer}} is used. 
Correct? 


was (Author: vahid):
[~junrao] How do you think the consumer group coordinator (I assume the broker 
id is sufficient) should be displayed in the output?
One option would be in a new {{COORDINATOR}} column (which repeats the same id 
in each row similar to how group name gets repeated):
{code}
GROUPCOORDINATORTOPIC   PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG  
  MEMBER-ID MEMBER-HOST  CLIENT-ID
group1   0  bar0  445 445 0 
 group1_kafka-1472762710305-24f2ffa3
  
{code}


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


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

2016-10-21 Thread Vahid Hashemian (JIRA)

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

Vahid Hashemian edited comment on KAFKA-3144 at 10/21/16 10:31 PM:
---

[~hachikuji] suggested that we report the coordinator id when {{--list}} option 
is used. [KAFKA-4333|https://issues.apache.org/jira/browse/KAFKA-4333] was 
created to track this improvement.


was (Author: vahid):
[~hachikuji] suggested that we report the coordinator id when {{--list}} option 
is used. I'll open a JIRA to address this request.

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


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

2016-06-14 Thread Vahid Hashemian (JIRA)

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


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

2016-06-16 Thread Vahid Hashemian (JIRA)

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

Vahid Hashemian edited comment on KAFKA-3144 at 6/16/16 5:05 PM:
-

[~hachikuji] Isn't what you are suggesting similar to what [~junrao] suggested 
at the very first comment 
[here|https://issues.apache.org/jira/browse/KAFKA-3144?focusedCommentId=15115594&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15115594]?
 If so, I suggested it to go under a different JIRA since scope-wise it is a 
bit different from the rest of this JIRA. Having said that I'm okay both ways.


was (Author: vahid):
[~hachikuji] Isn't what you are suggesting similar to what [~junrao] suggested 
at the very first comment 
[here|https://issues.apache.org/jira/browse/KAFKA-3144?focusedCommentId=15115594&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15115594]?

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