kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-4290) High CPU caused by timeout overflow in WorkerCoordinator
Date Tue, 11 Oct 2016 06:24:20 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564640#comment-15564640
] 

ASF GitHub Bot commented on KAFKA-4290:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/2009


> 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, 0.10.2.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)

Mime
View raw message