[jira] [Commented] (REEF-732) Provide a way to explicitly manage Driver lifetime

["Markus Weimer (JIRA)" <ji...@apache.org>]

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

Markus Weimer commented on REEF-732:
------------------------------------

Agreed. I'm not a huge fan of how we do this currently, and giving the application author control sounds like a good idea.

That said, a Driver can today gain control over its own life cycle by scheduling alarms for itself. As long as there is an alarm scheduled, the Driver does not shut down.

> Provide a way to explicitly manage Driver lifetime
> --------------------------------------------------
>
>                 Key: REEF-732
>                 URL: https://issues.apache.org/jira/browse/REEF-732
>             Project: REEF
>          Issue Type: New Feature
>          Components: REEF Driver, REEF.NET
>            Reporter: Anupam
>
> In current implementation, driver exits when it doesn't own any evaluator. This works for short lifetime jobs but might not work for long running services.
> We should provide a mechanism for driver author to explicitly manage Driver lifetime and exit only when the client or the Driver so desires.



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