[
https://issues.apache.org/jira/browse/KAFKA-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437761#comment-15437761
]
ASF GitHub Bot commented on KAFKA-3008:
---------------------------------------
GitHub user kkonstantine opened a pull request:
https://github.com/apache/kafka/pull/1788
KAFKA-3008: Parallel start and stop of connectors and tasks in Connect
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kkonstantine/kafka
KAFKA-3008-Parallel-start-and-stop-of-connectors-and-tasks
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1788.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1788
----
commit d1f876d4be7394688f6070169cded7748f8492cf
Author: Konstantine Karantasis <k.karanta...@gmail.com>
Date: 2016-08-25T05:38:45Z
KAFKA-3008: Parallel start and stop of connectors and tasks in Connect
Refactoring Worker to make start and stop methods thread safe.
commit 938b8ad2cba770dad71d3749b26ae59a3c4c3425
Author: Konstantine Karantasis <k.karanta...@gmail.com>
Date: 2016-08-25T21:31:57Z
Parallelizing start and stop of connectors and tasks in Distributed Herder
----
> Connect should parallelize task start/stop
> ------------------------------------------
>
> Key: KAFKA-3008
> URL: https://issues.apache.org/jira/browse/KAFKA-3008
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 0.9.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Liquan Pei
> Priority: Minor
>
> The Herder implementations currently iterate over all connectors/tasks and
> sequentially start/stop them. We should parallelize this. This is less
> critical for {{StandaloneHerder}}, but pretty important for
> {{DistributedHerder}} since it will generally be managing more tasks and any
> delay starting/stopping a single task will impact every other task on the
> node (and can ultimately result in incorrect behavior in the case of a single
> offset commit in one connector taking too long preventing all of the rest
> from committing offsets).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
