You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Vahid Hashemian (JIRA)" <ji...@apache.org> on 2016/05/03 19:25:13 UTC
[jira] [Commented] (KAFKA-3144) report members with no assigned
partitions in ConsumerGroupCommand
[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15269145#comment-15269145 ]
Vahid Hashemian commented on KAFKA-3144:
----------------------------------------
[~junrao] I haven't heard from [~Konrad Kalita] and have been thinking about this JIRA. Let's say I have two topics t1 and t2 with 3 partitions each. If I run a consumer consuming from both, and three others consuming from t1 (all belonging to the same group) would this be close to what you had in mind from an updated describe group command? Thanks.
GROUP TOPIC PARTITION CURRENT-OFFSET LOG-END-OFFSET LAG OWNER MEMBER-ID
cgroup1 t2 0 0 0 0 consumer-1_/127.0.0.1 consumer-1-7bdd36d8-ffcd-49f4-90b6-6a299e4a53b9
cgroup1 t1 1 3 3 0 consumer-1_/127.0.0.1 consumer-1-7bdd36d8-ffcd-49f4-90b6-6a299e4a53b9
cgroup1 t2 1 0 0 0 consumer-1_/127.0.0.1 consumer-1-7bdd36d8-ffcd-49f4-90b6-6a299e4a53b9
cgroup1 t2 2 0 0 0 consumer-1_/127.0.0.1 consumer-1-7bdd36d8-ffcd-49f4-90b6-6a299e4a53b9
cgroup1 t1 2 2 2 0 consumer-1_/127.0.0.1 consumer-1-b9612268-bc26-4194-999d-6dd77ef0793d
cgroup1 t1 0 1 1 0 consumer-1_/127.0.0.1 consumer-1-31588125-e6d2-4ad0-872d-32e0cd655ed1
cgroup1 consumer-1_/127.0.0.1 consumer-1-dadacb0f-7d80-4d26-9b54-b1f066a988e6
> 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: Konrad Kalita
> 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)