[EDGENT-8] Restart topology on uncaught exception

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Runtime
• Labels: failure-recovery
• Assignee: Victor Dogaru
• Reporter: Victor Dogaru
• Created: 08/Mar/16 17:33
• Updated: 20/Jun/16 17:32
• Resolved: 20/Jun/16 17:31

Description

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.