You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Anupam (JIRA)" <ji...@apache.org> on 2015/10/23 23:28:27 UTC

[jira] [Commented] (REEF-870) Need APIs for status tracking for .NET driver

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

Anupam commented on REEF-870:
-----------------------------

One idea:
We are focusing here on providing status on job completion.
We currently make decision to end a driver either on catastrophic failure or based on run-time heuristics that there is no more work to be done. In the case of catastrophic failure, our choices are limited and much more clearer. In case of determining driver lifetime based on heuristics we run into problems when the driver has a side channel not in control of the REEF layer, for example a separate RPC channel.
In case of failure the status are trivially defined and diagnostics need as much useful message as possible.
One possible way to solve the status plumbing and driver lifetime management would be to generate an event when REEF logic believes that there is no more work to be done, which the driver code can then respond to by providing us the status and message to be reported or by telling us that it is not ready to exit yet.

> Need APIs for status tracking for .NET driver
> ---------------------------------------------
>
>                 Key: REEF-870
>                 URL: https://issues.apache.org/jira/browse/REEF-870
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF Driver, REEF.NET Driver
>            Reporter: Anupam
>
> We need API for .NET driver to set status on success/failure, progress tracking and detailed diagnostics on job completion.
> Likely these APIs exist in Java driver, in which case this will reduce to plumbing.



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