You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Randall Hauch (Jira)" <ji...@apache.org> on 2019/10/15 16:15:00 UTC

[jira] [Resolved] (KAFKA-5741) Prioritize threads in Connect distributed worker process

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

Randall Hauch resolved KAFKA-5741.
----------------------------------
    Resolution: Won't Fix

Resolving as WONTFIX, since there is no clear indication that this is a problem.

> Prioritize threads in Connect distributed worker process
> --------------------------------------------------------
>
>                 Key: KAFKA-5741
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5741
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.11.0.0
>            Reporter: Randall Hauch
>            Priority: Critical
>
> Connect's distributed worker process uses the {{DistributedHerder}} to perform all administrative operations, including: starting, stopping, pausing, resuming, reconfiguring connectors; rebalancing; etc. The {{DistributedHerder}} uses a single threaded executor service to do all this work and to do it sequentially. If this thread gets preempted for any reason (e.g., connector tasks are bogging down the process, DoS, etc.), then the herder's membership in the group may be dropped, causing a rebalance.
> This herder thread should be run at a much higher priority than all of the other threads in the system.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)