[jira] [Commented] (QUARKS-8) Restart topology on uncaught exception

["Victor Dogaru (JIRA)" <ji...@apache.org>]

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

Victor Dogaru commented on QUARKS-8:
------------------------------------

Restarting the failed oplet path may run into issues when an Oplet is fed by multiple threads.


> Restart topology on uncaught exception
> --------------------------------------
>
>                 Key: QUARKS-8
>                 URL: https://issues.apache.org/jira/browse/QUARKS-8
>             Project: Quarks
>          Issue Type: New Feature
>          Components: Runtime
>            Reporter: Victor Dogaru
>            Assignee: Victor Dogaru
>
> If a Quarks thread abruptly terminates due to an uncaught exception the runtime shuts down. 
> A mechanism is needed to prevent the Quarks application from becoming unavailable:
> * Have a monitor service which resubmits the topology in case it shuts down.
> * Restart the failed oplet. In the ETIAO runtime, a source and all downstream oplet invocations (up to an Isolate) will execute in the same thread, so the runtime needs to restart the failed path.



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