You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/05/09 07:13:12 UTC

[jira] [Resolved] (KAFKA-3674) Connector target state changes not propagated to all workers

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

Ewen Cheslack-Postava resolved KAFKA-3674.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.1.0

Issue resolved by pull request 1341
[https://github.com/apache/kafka/pull/1341]

> 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
>             Fix For: 0.10.1.0, 0.10.0.0
>
>
> 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)