[
https://issues.apache.org/jira/browse/KAFKA-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883402#comment-16883402
]
Konstantine Karantasis commented on KAFKA-5741:
-----------------------------------------------
[~rhauch] [~ewencp] do we think this is still important after
https://issues.apache.org/jira/browse/KAFKA-5505 and
https://cwiki.apache.org/confluence/display/KAFKA/KIP-415%3A+Incremental+Cooperative+Rebalancing+in+Kafka+Connect
?
If not maybe we could close this ticket.
> 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
(v7.6.14#76016)
