You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2016/10/11 03:43:20 UTC

[jira] [Created] (KAFKA-4290) High CPU caused by timeout overflow in WorkerCoordinator

Jason Gustafson created KAFKA-4290:
--------------------------------------

             Summary: 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)