reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1378) Evaluator Manager for IMRU
Date Tue, 03 May 2016 16:46:12 GMT

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

Markus Weimer commented on REEF-1378:
-------------------------------------

{quote}
This is because Evaluator can fail before context is loaded/recorded. And we receive them
in separated events as well. 
{quote}

Thanks! That was what I was missing. However, we might not have to track Evaluators specifically:
If an Evaluator fails between {{AllocatedEvaluator}} and the first {{ActiveContext}}, we get
an {{IFailedEvaluator}}. In the handler for that event, we request a new Evaluator anyhow,
right? What else do we need to do differently in this case from later in the computation?

Note that I am pushing back on more state in the Driver, not on more classes. The reason is
that we eventually want this Driver to also be restartable. And every bit of state we keep
complicates that matter. 

> Evaluator Manager for IMRU
> --------------------------
>
>                 Key: REEF-1378
>                 URL: https://issues.apache.org/jira/browse/REEF-1378
>             Project: REEF
>          Issue Type: Task
>          Components: IMRU, REEF.NET
>            Reporter: Julia
>            Assignee: Julia
>         Attachments: EvaluatorManager.cs
>
>
> Booking tracking allocated Evaluators, failed Evalators. Provided methods to add/remove
evaluators and request evaluators. 



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

Mime
View raw message