[
https://issues.apache.org/jira/browse/KAFKA-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484394#comment-16484394
]
ASF GitHub Bot commented on KAFKA-6028:
---------------------------------------
jonlee2 opened a new pull request #5064: KAFKA-6028: Improve the quota throttle
communication (KIP-219)
URL: https://github.com/apache/kafka/pull/5064
This PR is a continuation from https://github.com/apache/kafka/pull/4830. I
create a new PR because the original PR got big and it looks like some
reviewers are having problems with loading it. I also used a new branch.
This implements KIP-219, where a broker return a response with throttle time
on quota violation immediately after processing the corresponding request.
After the response is sent out, the broker will keep the channel muted until
the throttle time is over. Also, on receiving a response with throttle time,
client will also block outgoing communication to the broker for the specified
throttle time.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Improve the quota throttle communication.
> -----------------------------------------
>
> Key: KAFKA-6028
> URL: https://issues.apache.org/jira/browse/KAFKA-6028
> Project: Kafka
> Issue Type: Improvement
> Components: clients, core
> Affects Versions: 1.0.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Priority: Major
> Fix For: 2.0.0
>
>
> Currently if a client is throttled duet to quota violation, the broker will
> only send back a response to the clients after the throttle time has passed.
> In this case, the clients don't know how long the response will be throttled
> and might hit request timeout before the response is returned. As a result
> the clients will retry sending a request and results a even longer throttle
> time.
> The above scenario could happen when a large clients group sending records to
> the brokers. We saw this when a MapReduce job pushes data to the Kafka
> cluster.
> To improve this, the broker can return the response with throttle time
> immediately after processing the requests. After that, the broker will mute
> the channel for this client. A correct client implementation should back off
> for that long before sending the next request. If the client ignored the
> throttle time and send the next request immediately, the channel will be
> muted and the request won't be processed until the throttle time has passed.
> A KIP will follow with more details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
