[
https://issues.apache.org/jira/browse/KAFKA-10897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyijun updated KAFKA-10897:
------------------------------
Comment: was deleted
(was: Not yet)
> kafka quota optimization
> ------------------------
>
> Key: KAFKA-10897
> URL: https://issues.apache.org/jira/browse/KAFKA-10897
> Project: Kafka
> Issue Type: Improvement
> Components: admin, clients, config, consumer, core
> Affects Versions: 2.7.0
> Reporter: yangyijun
> Priority: Blocker
>
> *1.The current quota dimensions is as follows:*
> {code:java}
> /config/users/<user>/clients/<client-id>
> /config/users/<user>/clients/<default>
> /config/users/<user>
> /config/users/<default>/clients/<client-id>
> /config/users/<default>/clients/<default>
> /config/users/<default>
> /config/clients/<client-id>
> /config/clients/<default>{code}
> *2. Existing problems:*
>
> {code:java}
> 2.1.The quota dimensions is not fine enough.
> 2.2.When multiple users on the same broker produce and consume a large amount
> of data at the same time, if you want the broker to run normally, you must
> make the sum of all user quota byte not exceed the upper throughput limit of
> the broker.
> 2.3.Even if all the user rate does not reach the upper limit of the broker,
> but all the user rate is concentrated on a few disks and exceeds the
> read-write load of the disk, all the produce and consume requests will be
> blocked.
> 2.4.Sometimes it's just one topic rate increase sharply under the user, so we
> just need to limit the increase sharply topics.
> {code}
>
> *3. Suggestions for improvement*
> {code:java}
> 3.1. Add the upper limit of single broker quota byte.
> 3.2. Add the upper limit of single disk quota byte on the broker.
> 3.3. Add topic quota dimensions.{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
