[
https://issues.apache.org/jira/browse/KAFKA-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858410#comment-15858410
]
Jun Rao commented on KAFKA-4195:
--------------------------------
Ismael brought up a good point that it may not be easy to set a request rate
limit (e.g., is it 10/sec or 100/sec). An alternative way is to model the
request handler pool as shared resource and allow the admin to set a max
percentage (e.g., 5%) that a user/client can use. This should cover the case
when a client floods the broker with many requests and potentially some other
bad cases.
Implementation wise, we can measure the faction of request handler capacity
used in KafkaApis.handle() and delay the processing of the request if the limit
is exceeded.
We also may need to think a bit on how to integrate the new throttling with the
existing throttling that we already have on byte rate in producer/consumer and
followers.
> support throttling on request rate
> ----------------------------------
>
> Key: KAFKA-4195
> URL: https://issues.apache.org/jira/browse/KAFKA-4195
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jun Rao
> Assignee: Rajini Sivaram
>
> Currently, we can throttle the client by data volume. However, if a client
> sends requests too quickly (e.g., a consumer with min.byte configured to 0),
> it can still overwhelm the broker. It would be useful to additionally support
> throttling by request rate.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
