kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wenjie Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6219) Inconsistent behavior for kafka-consumer-groups
Date Tue, 05 Dec 2017 19:33:00 GMT

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

Wenjie Zhang commented on KAFKA-6219:

We are seeing the similar issue. Basically, we have the ACL configured, the read is opened
to all IPs, but the write is restricted to a few IPs.
When running `bin/kafka-consumer-groups.sh --list --bootstrap-server`, it does not return
anything, but running `bin/kafka-consumer-groups.sh  --describe -group` works fine.

> 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
> For example, 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

View raw message