reef-dev mailing list archives

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

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

Dhruv Mahajan commented on REEF-1378:
-------------------------------------

[~juliaw] Please refer to my comments above for some discussion on state maintenance. Moreover,
call like {{AddContextLoadedEvalutor}} in {{EvaluatorManager}} will always be preceded/succeeded
by {{Add}} call in {{ActiveContextManager}}.

So it seems there are some overlaps in functionalities that probably can be removed. Moreover,
if it's a {{EvaluatorManager}} class keeping all the info for various stages, why is it not
taking care of Task stage of evaluator. Can we first define clearly the scope of this class
and what we want to do with it clearly?

In my understanding you have {{ActiveContextManager}} class where you put all the {{IActiveContexts}}.
In a similar way you can have {{AllocatedEvaluatorManager}} class that handles loading root
context configuration (data loading) using Partition descriptors. Now any failure happens,
driver can notify all these managers who take appropriate actions.

> 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