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

jin xing edited comment on KAFKA-3093 at 2/15/16 4:43 PM:
----------------------------------------------------------

[~hachikuji]
It's great if you can work on this;
I like the idea to differentiate connector's target state from runtime state;
It make sense to catch exceptions thrown when running tasks and avoid 
connector's jvm from falling down and mark the connector to be failed state;
One question, do we take some measures when the connector's state is 'failed';
e.g. when send a wrong connector config, the connector failed, do we just leave 
it there or roll back the connector's config and restart the connector?
(I was on a vacation and failed to track this jira, it's great to help this if 
possible, or do you wanna separate this ticket into small ones?)


was (Author: jinxing6...@126.com):
[~hachikuji]
It's great if you can work on this;
I like the idea to differentiate connector's target state from runtime state;
It make sense to catch exceptions thrown when running tasks and avoid 
connector's jvm from falling down and mark the connector to be failed state;
One question, do we take some measures when the connector's state is 'failed';
e.g. when send a wrong connector config, the connector failed, do we just leave 
it there or roll back the connector's config and restart the connector?

> Keep track of connector and task status info, expose it via the REST API
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-3093
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3093
>             Project: Kafka
>          Issue Type: Improvement
>          Components: copycat
>            Reporter: jin xing
>            Assignee: Jason Gustafson
>
> Relate to KAFKA-3054;
> We should keep track of the status of connector and task during their 
> startup, execution, and handle exceptions thrown by connector and task;
> Users should be able to fetch these informations by REST API and send some 
> necessary commands(reconfiguring, restarting, pausing, unpausing) to 
> connectors and tasks by REST API;



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

Reply via email to