kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jin xing (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3054) Connect Herder fail forever if sent a wrong connector config or task config
Date Mon, 11 Jan 2016 14:44:39 GMT

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

jin xing commented on KAFKA-3054:
---------------------------------

[~ewencp]
thanks for comment : )
currently the DistributedHerder only catch the ConfigException,  thus any other exceptions
thrown during connector startup or task startup will kill the DistributedHerder and Worker;
If the cluster has only one DistributedHerder, restart will fail forever; 
It make sense to let the herder swallow all exceptions thrown by connector or task during
handling the life cycle of connector and task, thus Herder and Worker can keep running;
How do you think?


> 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)

Mime
View raw message