[
https://issues.apache.org/jira/browse/KAFKA-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427362#comment-15427362
]
Shikhar Bhushan commented on KAFKA-3054:
----------------------------------------
Addressing this in KAFKA-4042, which should take care of remaining robustness
issues in the {{DistributedHerder}} from bad connector or task configs.
> 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)
