You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "huxihx (JIRA)" <ji...@apache.org> on 2017/11/16 06:41:01 UTC

[jira] [Updated] (KAFKA-6219) Inconsistent behavior for kafka-consumer-groups

     [ https://issues.apache.org/jira/browse/KAFKA-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

huxihx updated KAFKA-6219:
--------------------------
    Summary: Inconsistent behavior for kafka-consumer-groups  (was: Inconsistent behavior for kafka-consumer-groups with ACL enabled)

> Inconsistent behavior for kafka-consumer-groups
> -----------------------------------------------
>
>                 Key: KAFKA-6219
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6219
>             Project: Kafka
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 1.0.0
>            Reporter: huxihx
>            Assignee: huxihx
>
> When ACL is enabled, running kafka-consumer-groups.sh --describe to describe a group complains:
> `Error: Executing consumer group command failed due to Not authorized to access group: Group authorization failed.`
> However, running kafka-consumer-groups.sh --list otherwise returns nothing, confusing user whether there are no groups at all or something wrong happened.
> In `AdminClient.listAllGroups`, it captures all the possible exceptions and returns an empty List.
> It's better keep those two methods consistent. Does it make any sense?



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