[
https://issues.apache.org/jira/browse/KAFKA-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275302#comment-15275302
]
ASF GitHub Bot commented on KAFKA-3674:
---------------------------------------
GitHub user hachikuji opened a pull request:
https://github.com/apache/kafka/pull/1341
KAFKA-3674: Ensure connector target state changes propagated to worker
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hachikuji/kafka KAFKA-3674
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1341.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 #1341
----
commit cc6ea79edb2f7b734b0e277ac1b7d3cc231064fb
Author: Jason Gustafson <ja...@confluent.io>
Date: 2016-05-07T01:04:14Z
KAFKA-3674: Ensure connector target state changes propagated to worker
----
> Connector target state changes not propagated to all workers
> ------------------------------------------------------------
>
> Key: KAFKA-3674
> URL: https://issues.apache.org/jira/browse/KAFKA-3674
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Blocker
>
> Current handling of target state changes to a connector in DistributedHerder
> seems dubious. We don't appear to propagate changes to the worker unless it
> is running the connector itself, which means tasks running on separate
> workers will not be notified of state changes. This should have been caught
> with unit tests, but current coverage seems quite poor, so we should improve
> that as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
