[
https://issues.apache.org/jira/browse/KAFKA-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564425#comment-15564425
]
ASF GitHub Bot commented on KAFKA-4290:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/2009
KAFKA-4290: Fix timeout overflow in WorkerCoordinator.poll
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-4290
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2009.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2009
----
commit 50c65a82923fc62b3f4b73812097bcc01aa74fef
Author: Jason Gustafson <[email protected]>
Date: 2016-10-11T04:27:45Z
KAFKA-4290: Fix timeout overflow in WorkerCoordinator.poll
----
> High CPU caused by timeout overflow in WorkerCoordinator
> --------------------------------------------------------
>
> Key: KAFKA-4290
> URL: https://issues.apache.org/jira/browse/KAFKA-4290
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Blocker
> Fix For: 0.10.1.0
>
>
> The timeout passed to {{WorkerCoordinator.poll()}} can overflow if large
> enough because we add it to the current time in order to calculate the call's
> deadline. This shortcuts the poll loop and results in a very tight event loop
> which can saturate a CPU. We hit this case out of the box because Connect
> uses a default timeout of {{Long.MAX_VALUE}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
