edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Victor Dogaru (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (QUARKS-8) Restart topology on uncaught exception
Date Mon, 20 Jun 2016 17:32:05 GMT

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

Victor Dogaru resolved QUARKS-8.
--------------------------------
    Resolution: Fixed

This issue has been resolved by adding a [Job monitoring application|https://issues.apache.org/jira/browse/QUARKS-66].

> 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)

Mime
View raw message