[
https://issues.apache.org/jira/browse/KAFKA-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584969#comment-16584969
]
ASF GitHub Bot commented on KAFKA-7311:
---------------------------------------
rodesai opened a new pull request #5531: KAFKA-7311: Reset next batch expiry
time on each poll loop
URL: https://github.com/apache/kafka/pull/5531
*More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.*
*Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.*
### 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
> Sender should reset next batch expiry time between poll loops
> -------------------------------------------------------------
>
> Key: KAFKA-7311
> URL: https://issues.apache.org/jira/browse/KAFKA-7311
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 2.1.0
> Reporter: Rohan Desai
> Priority: Major
> Fix For: 2.1.0
>
>
> Sender does not reset next batch expiry time between poll loops. This means
> that once it crosses the expiry time of the first batch, it starts spinning
> on epoll with a timeout of 0, which consumes a lot of CPU. We observed this
> running KSQL when investigating why throughput would drop after about 10
> minutes (the default delivery timeout).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
