[jira] [Created] (KAFKA-9658) Removing default user quota doesn't take effect until broker restart

["Anna Povzner (Jira)" <ji...@apache.org>]

Anna Povzner created KAFKA-9658:
-----------------------------------

             Summary: Removing default user quota doesn't take effect until broker restart
                 Key: KAFKA-9658
                 URL: https://issues.apache.org/jira/browse/KAFKA-9658
             Project: Kafka
          Issue Type: Bug
    Affects Versions: 2.3.1, 2.4.0, 2.2.2, 2.1.1, 2.0.1
            Reporter: Anna Povzner
            Assignee: Anna Povzner


To reproduce (for any quota type: produce, consume, and request):

Example with consumer quota, assuming no user/client quotas are set initially.
1. Set default user consumer quotas:

{{./kafka-configs.sh --zookeeper <ZK> --alter --add-config 'consumer_byte_rate=100000000' --entity-type users --entity-default}}

{{2. Send some consume load for some user, say user1.}}

{{3. Remove default user consumer quota using:}}
{{./kafka-configs.sh --zookeeper <ZK> --alter --delete-config 'consumer_byte_rate' --entity-type users --entity-default}}

Result: --describe (as below) returns correct result that there is no quota, but quota bound in ClientQuotaManager.metrics does not get updated for users that were sending load, which causes the broker to continue throttling requests with the previously set quota.
 {{/opt/confluent/bin/kafka-configs.sh --zookeeper <ZK>  --describe --entity-type users --entity-default}}
{{}}{{}} 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)