You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Janardhana Gopalachar (Jira)" <ji...@apache.org> on 2024/05/09 17:32:00 UTC
[jira] [Updated] (KAFKA-16693) Kafka Users are created with ACL entries and during performing operations allowed by ACL we see Denied Operation
[ https://issues.apache.org/jira/browse/KAFKA-16693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Janardhana Gopalachar updated KAFKA-16693:
------------------------------------------
Description:
Hi
We have created 2 KafkaUsers from Strimzi operator for 2 different cluster with ACL entries. we have observed that the ACL entries in teh Kafka Cluster will not be present for approximately 4 minutes and the ACL entries will be available after that. The clients which are using KafkaUser to perform operations not be able to perform operations till the ACL is available in KafkaCLuster.
We see in the Kafka Logs below are the mesages the user and cluster details in messages are not added since it is proprietery
Processing notification(s) to /config/change
Processing override for entityPath
Removing PRODUCE quota for user
Removing FETCH quota for user
Removing REQUEST quota for user
Removing CONTROLLER_MUTATION quota for user
Processing notification(s) to /kafka-acl-changes
Processing Acl change notification for
Processing notification(s) to /config/changes
Processing notification(s) to /kafka-acl-changes
Processing Acl change notification for ResourcePattern(resourceType=GROU
The same behavior is observed even if we create a single KafkaUser , same behavior is observed
was:
Hi
We have created 2 KafkaUsers from Strimzi operator for 2 different cluster with ACL entries. we have observed that the ACL entries in teh Kafka Cluster will not be present for approximately 4 minutes and the ACL entries will be available after that. The clients which are using KafkaUser to perform operations not be able to perform operations till the ACL is available in KafkaCLuster.
We see in the Kafka Logs below are the mesages the user and cluster details in messages are not added since it is proprietery
Processing notification(s) to /config/change
Processing override for entityPath
Removing PRODUCE quota for user
Removing FETCH quota for user
Removing REQUEST quota for user
Removing CONTROLLER_MUTATION quota for user
Processing notification(s) to /kafka-acl-changes
Processing Acl change notification for
Processing notification(s) to /config/changes
Processing notification(s) to /kafka-acl-changes
Processing Acl change notification for ResourcePattern(resourceType=GROU
> Kafka Users are created with ACL entries and during performing operations allowed by ACL we see Denied Operation
> ----------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-16693
> URL: https://issues.apache.org/jira/browse/KAFKA-16693
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 3.5.1
> Reporter: Janardhana Gopalachar
> Priority: Blocker
>
> Hi
> We have created 2 KafkaUsers from Strimzi operator for 2 different cluster with ACL entries. we have observed that the ACL entries in teh Kafka Cluster will not be present for approximately 4 minutes and the ACL entries will be available after that. The clients which are using KafkaUser to perform operations not be able to perform operations till the ACL is available in KafkaCLuster.
> We see in the Kafka Logs below are the mesages the user and cluster details in messages are not added since it is proprietery
>
> Processing notification(s) to /config/change
> Processing override for entityPath
> Removing PRODUCE quota for user
> Removing FETCH quota for user
> Removing REQUEST quota for user
> Removing CONTROLLER_MUTATION quota for user
> Processing notification(s) to /kafka-acl-changes
> Processing Acl change notification for
> Processing notification(s) to /config/changes
> Processing notification(s) to /kafka-acl-changes
> Processing Acl change notification for ResourcePattern(resourceType=GROU
>
> The same behavior is observed even if we create a single KafkaUser , same behavior is observed
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)