[
https://issues.apache.org/jira/browse/SAMZA-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15997939#comment-15997939
]
Navina Ramesh commented on SAMZA-1150:
--------------------------------------
For simplicity and to be robust for 0.13.0 release timeline, we are going to
treat all error conditions as FATAL in jobcoordinator and shutdown the
streamprocessor.
A complete solution addressing the questions listed in this JIRA will be done
in a follow-up release.
> 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
> Assignee: Navina Ramesh
> Fix For: 0.13.0
>
>
> 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)
