[
https://issues.apache.org/jira/browse/KAFKA-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872991#comment-17872991
]
Jun Rao commented on KAFKA-15863:
---------------------------------
[~sjhajharia] : A couple of things.
(1) If a client sends too many telemetric requests, it means that it's a bad
client. In this case, it's ok to mute the channel shared with the
producer/consumer since the main goal is to protect the server against the bad
client. There is no need to save the producer/fetch request from this bad
client.
(2) Regarding the PushIntervalMs quota implementation, is the functionality
already achieved by the request quota? If so, we probably don't need a separate
PushIntervalMs quota. If not, we could implement PushIntervalMs quota by muting
the shared client channel.
> Handle push telemetry throttling with quota manager
> ---------------------------------------------------
>
> Key: KAFKA-15863
> URL: https://issues.apache.org/jira/browse/KAFKA-15863
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Apoorv Mittal
> Assignee: Sanskar Jhajharia
> Priority: Major
>
> Details: https://github.com/apache/kafka/pull/14699#discussion_r1399714279
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
