[
https://issues.apache.org/jira/browse/KAFKA-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247982#comment-15247982
]
ASF GitHub Bot commented on KAFKA-3586:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/1238
KAFKA-3586: Revert to default quota when client quota override is deleted
Update client quota when override is deleted from config
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-3586
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1238.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1238
----
commit 0079c01ee7a78710f08a5ebf7834380f5d5ff1b0
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date: 2016-04-19T15:07:39Z
KAFKA-3586: Revert to default quota when quota override is deleted for
client
----
> Quotas do not revert to default values when override config is deleted
> ----------------------------------------------------------------------
>
> Key: KAFKA-3586
> URL: https://issues.apache.org/jira/browse/KAFKA-3586
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.9.0.1
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
>
> When quota override configuration for a clientId is updated (eg using
> kafka-configs.sh), the quotas of the client are dynamically updated by the
> broker. But when the quota override configuration is deleted, the changes are
> ignored (until broker restart). It would make sense for the client's quotas
> to revert to the default quota configuration when the override is removed
> from the config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
