You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Cazen Lee (JIRA)" <ji...@apache.org> on 2016/04/27 03:29:12 UTC
[jira] [Commented] (QUARKS-8) Restart topology on uncaught
exception
[ https://issues.apache.org/jira/browse/QUARKS-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259335#comment-15259335 ]
Cazen Lee commented on QUARKS-8:
--------------------------------
It appears that the work is already finished. Is it possible to close this issue?
> 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
> Labels: failure-recovery
>
> 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)