You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2017/06/27 14:13:00 UTC

[jira] [Commented] (KAFKA-5526) ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets

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

Ismael Juma commented on KAFKA-5526:
------------------------------------

[~vahid], any idea what's going on here? 

> ConsumerGroupCommand no longer shows output for consumer groups which have not committed offsets
> ------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5526
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5526
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Ryan P
>
> It would appear that the latest iteration of the ConsumerGroupCommand no longer outputs information about group membership when no offsets have been committed. It would be nice if the output generated by these tools maintained some form of consistency across versions as some users have grown to depend on them. 
> 0.9.x output:
> bin/kafka-consumer-groups --bootstrap-server localhost:9092 --new-consumer --describe --group console-consumer-34885
> GROUP, TOPIC, PARTITION, CURRENT OFFSET, LOG END OFFSET, LAG, OWNER
> console-consumer-34885, test, 0, unknown, 0, unknown, consumer-1_/192.168.1.64
> 0.10.2 output:
> bin/kafka-consumer-groups --bootstrap-server localhost:9092 --new-consumer --describe --group console-consumer-34885
> Note: This will only show information about consumers that use the Java consumer API (non-ZooKeeper-based consumers).
> TOPIC                          PARTITION  CURRENT-OFFSET  LOG-END-OFFSET  LAG        CONSUMER-ID                                       HOST                           CLIENT-ID



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)