[
https://issues.apache.org/jira/browse/KAFKA-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081370#comment-15081370
]
Ewen Cheslack-Postava commented on KAFKA-3054:
----------------------------------------------
[~jinxing6...@126.com] Yes, this sounds like a bug. In general I think there
are a number of places where we need to do a better job handling errors -- e.g.
this is during startup, but also during execution of tasks when an error can
keep happening repeatedly such that a task can't even make any progress
(whether the issue is in Connect or the other system). In order to better
handle this generally we're going to need to keep track of status info, expose
it via the REST API, and allow users to take corrective action (e.g.
reconfiguring, restarting tasks, etc).
However, that's a pretty big project. For this bug, it sounds like we're just
missing a {{catch}} block during connector/task startup which we should instead
be catching and then handling by, at a minimum, logging some info at {{ERROR}}
level.
> 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: copycat
> Affects Versions: 0.9.0.0
> Reporter: jin xing
> Assignee: jin xing
>
> 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)
