You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2017/03/17 01:18:41 UTC

[jira] [Created] (SAMZA-1150) Handling Error propagation between ZkJobCoordinator & DebounceTimer

Navina Ramesh created SAMZA-1150:
------------------------------------

             Summary: 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? 




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