You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mahsa Seifikar (Jira)" <ji...@apache.org> on 2025/05/16 16:04:00 UTC
[jira] [Updated] (KAFKA-19282) Update quotaTypesEnabled on quota removal in ClientQuotaManager
[ https://issues.apache.org/jira/browse/KAFKA-19282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahsa Seifikar updated KAFKA-19282:
-----------------------------------
Description: In kafka.server.ClientQuotaManager class, quotaTypesEnabled is not updated when a quota is removed via removeQuota method in DefaultQuotaCallback class. This field is set when quotas are added in updateQuota but it's never changed or cleared. This can lead to incorrect behaviour in the quotasEnabled method. So in case all the quotas have been removed dynamically, the system may incorrectly assume the quotas are active, which leads to unnecessary metric creation or updates until the broker is restarted. (was: In kafka.server.ClientQuotaManager class, quotaTypesEnabled is not updated when a quota is removed via removeQuota method in DefaultQuotaCallback class. This field is set when quotas are added in updateQuota but it's never changed or cleared. This can lead to incorrect behaviour in the quotaEnabled method. So in case all the quotas have been removed dynamically, the system may incorrectly assume the quotas are active, which leads to unnecessary metric creation or updates until the broker is restarted. )
> Update quotaTypesEnabled on quota removal in ClientQuotaManager
> ---------------------------------------------------------------
>
> Key: KAFKA-19282
> URL: https://issues.apache.org/jira/browse/KAFKA-19282
> Project: Kafka
> Issue Type: Bug
> Reporter: Mahsa Seifikar
> Assignee: Mahsa Seifikar
> Priority: Major
>
> In kafka.server.ClientQuotaManager class, quotaTypesEnabled is not updated when a quota is removed via removeQuota method in DefaultQuotaCallback class. This field is set when quotas are added in updateQuota but it's never changed or cleared. This can lead to incorrect behaviour in the quotasEnabled method. So in case all the quotas have been removed dynamically, the system may incorrectly assume the quotas are active, which leads to unnecessary metric creation or updates until the broker is restarted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)