You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "Andrew Chung (JIRA)" <ji...@apache.org> on 2015/08/04 21:55:05 UTC

[jira] [Assigned] (REEF-541) Notifying evaluator restart failure entails calling AllocatedEvaluatorHandler

     [ https://issues.apache.org/jira/browse/REEF-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Chung reassigned REEF-541:
---------------------------------

    Assignee: Andrew Chung

> Notifying evaluator restart failure entails calling AllocatedEvaluatorHandler
> -----------------------------------------------------------------------------
>
>                 Key: REEF-541
>                 URL: https://issues.apache.org/jira/browse/REEF-541
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF Driver, REEF.NET Driver
>            Reporter: Andrew Chung
>            Assignee: Andrew Chung
>
> On restarts, if an evaluator fails, we need to create a brand new EvaluatorManager for it, which calls AllocatedEvaluatorHandler. This does not really make sense as the evaluator was never really "allocated," and we should call EvaluatorFailedHandler directly. In addition, in the C# interop portion for AllocatedEvaluatorHandler, we inspect fields in the Evaluator object, which causes a NullReferenceException because on restarts, we do not initialize certain fields for the "allocated" evaluator. Perhaps there should be a new EvaluatorFailed handler specifically for restarts as well.



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