[
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}
GROUP COORDINATOR TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG
MEMBER-ID MEMBER-HOST CLIENT-ID
group1 0 bar 0 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}
GROUP COORDINATOR TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG
MEMBER-ID MEMBER-HOST CLIENT-ID
group1 0 bar 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)