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

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

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

Ewen Cheslack-Postava updated KAFKA-3054:
-----------------------------------------
         Priority: Blocker  (was: Major)
    Fix Version/s: 0.10.1.0

We improved error handling in 0.10.0.0. In theory we should be catching and handling these errors, marking the connector/task as dead. However, we should make sure we have a test covering this specific case to validate the handling before marking this resolved. And we should make sure we cover *both* types of invalid configs for *both* types of connectors -- since we do some initial parsing of configs to setup the connector within the framework and then the connector does its own parsing, we should make sure all failure scenarios are handled.

> 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: jin xing
>            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)