You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/12/26 22:38:58 UTC

[jira] [Commented] (KAFKA-3054) Connect Herder fail forever if sent a wrong connector config or task config

    [ https://issues.apache.org/jira/browse/KAFKA-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779106#comment-15779106 ] 

ASF GitHub Bot commented on KAFKA-3054:
---------------------------------------

Github user pono closed the pull request at:

    https://github.com/apache/kafka/pull/782


> Connect Herder fail forever if sent a wrong connector config or task config
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-3054
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3054
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.9.0.0
>            Reporter: jin xing
>            Assignee: Shikhar Bhushan
>            Priority: Blocker
>             Fix For: 0.10.1.0
>
>
> Connector Herder throws ConnectException and shutdown if sent a wrong config, restarting herder will keep failing with the wrong config; It make sense that herder should stay available when start connector or task failed; After receiving a delete connector request, the herder can delete the wrong config from "config storage"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)