reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhruv Mahajan (JIRA)" <>
Subject [jira] [Commented] (REEF-1419) Job status and metrics reporting in IMRU
Date Sat, 04 Jun 2016 18:10:59 GMT


Dhruv Mahajan commented on REEF-1419:

[~markus.weimer] [~afchung90], I would like to start some discussion on this. There are two
aspects of this:

a) From IMRU tasks to Driver: We assume that Update function can generate job status after
every iteration and communicate it back to driver. We can define a serializable {{IMRUJobStatus}}
interface and ask the user to provide its impementation as part of IMRUJobDefinition. The
instance of this type can then be communicated from Update function to driver. We can discuss
how to do this communication and other details here later once we converge higher level design.

b) From Driver to Client: I believe the appropriate structure here is IJobSubmissionResult.
I am not well versed with the functionality and semantics of this part of the code. I tried
looking at the code and REEF documentation but it still was not clear to me. What is the way,
for client to ask for job status via IJobSubmissionResult or for driver to push it. Which
mechanism of the two (driver pushes vs. driver reacts) do we support. My guess is that it
is reactive.

Moreover while whatever we do in a) is limited to IMRU, b) can be made more generic and beyond
IMRU itself right?
Please share your thoughts.

> Job status and metrics reporting in IMRU
> ----------------------------------------
>                 Key: REEF-1419
>                 URL:
>             Project: REEF
>          Issue Type: New Feature
>          Components: REEF.NET
>         Environment: C#
>            Reporter: Dhruv Mahajan
> Currently, when any external application uses IMRU client to start an IMRU job, there
is no way to register and get a Job status back periodically.
> First of all, the job status needs to be communicated from evaluators to driver and then
driver needs to communicate it back to client.
> The aim of this JIRA is to discuss and converge on possible solution and then implement

This message was sent by Atlassian JIRA

View raw message