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

Navina Ramesh updated SAMZA-1150:
---------------------------------
    Description: 
Right now, I don't think we handle errors from any of the callback properly. As 
far as I can tell, most of the errors should cause the processor to stop and 
propagate the error to the user. But we need to carefully evaluate the various 
error scenarios.
Through this JIRA, we need to answer the following:
1. How to handle errors/exceptions thrown in the callbacks that are executed 
with the debounce timer?
2. Debounce timer has a category of tasks to run. What happens when one task 
fails? Do we cancel the other pending tasks, if any ? Does the ordering of the 
tasks matter at all? 
3. What kind of failures should be considered FATAL? 

  was:
Right now, I don't think we handle errors from any of the callback properly. As 
far as I can tell, most of the errors should cause the processor to stop and 
propagate the error to the user. But we need to carefully evaluate the various 
error scenarios.
Through this JIRA, we need to answer the following:
1. How to handle errors/exceptions thrown in the callbacks that are executed 
with the debounce timer?
2. Debounce timer has a category of tasks to run. What happens when one task 
fails? Do we cancel the other pending tasks, if any ? Does the ordering of the 
tasks matter at all? 



> Handling Error propagation between ZkJobCoordinator & DebounceTimer
> -------------------------------------------------------------------
>
>                 Key: SAMZA-1150
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1150
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Navina Ramesh
>
> Right now, I don't think we handle errors from any of the callback properly. 
> As far as I can tell, most of the errors should cause the processor to stop 
> and propagate the error to the user. But we need to carefully evaluate the 
> various error scenarios.
> Through this JIRA, we need to answer the following:
> 1. How to handle errors/exceptions thrown in the callbacks that are executed 
> with the debounce timer?
> 2. Debounce timer has a category of tasks to run. What happens when one task 
> fails? Do we cancel the other pending tasks, if any ? Does the ordering of 
> the tasks matter at all? 
> 3. What kind of failures should be considered FATAL? 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to