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

Posted to jira@kafka.apache.org by "YeLiang (JIRA)" <ji...@apache.org> on 2019/02/03 03:30:00 UTC

[jira] [Assigned] (KAFKA-7880) KafkaConnect should standardize worker thread name

     [ https://issues.apache.org/jira/browse/KAFKA-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

YeLiang reassigned KAFKA-7880:
------------------------------

    Assignee: YeLiang

> KafkaConnect should standardize worker thread name
> --------------------------------------------------
>
>                 Key: KAFKA-7880
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7880
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 2.1.0
>            Reporter: YeLiang
>            Assignee: YeLiang
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> KafkaConnect will create a WorkerTask for tasks assigned to it and then submit tasks to a thread pool.
> However,the [Worker|https://github.com/apache/kafka/blob/2.1.0/connect/runtime/src/main/java/org/apache/kafka/connect/runtime/Worker.java] class initializes its thread pool using a default ThreadFactory.So the thread name will have a pattern pool-[0-9]\-thread\-[0-9].
> When we are running KafkaConnect and find that one of the task thread is under high CPU usage, it is difficult for us to find out which task is under high load becasue when we print out the stack of KafkaConnect, we can only see a list of threads name pool-[0-9]\-thread\-[0-9] even if we can know the exact pid of the high CPU usage thread
> If worker threads name will be named like connectorName-taskId, it will be very helpful



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)