You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2016/09/02 00:38:20 UTC
[jira] [Resolved] (REEF-1251) IMRU Driver handlers for Fault
Tolerant
[ https://issues.apache.org/jira/browse/REEF-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julia resolved REEF-1251.
-------------------------
Resolution: Fixed
Fix Version/s: 0.16
Resolved via https://github.com/apache/reef/pull/1087
> IMRU Driver handlers for Fault Tolerant
> ---------------------------------------
>
> Key: REEF-1251
> URL: https://issues.apache.org/jira/browse/REEF-1251
> Project: REEF
> Issue Type: Task
> Components: REEF.NET, REEF.NET Evaluator
> Reporter: Julia
> Assignee: Julia
> Labels: FT
> Fix For: 0.16
>
>
> Handles communications between driver and evaluators for evaluator and task recovery when some evaluators fail. The following describe a flow for an example:
> Here is the control flow in normal scenario:
> a. All the task, context and task status information is maintained in Task Manager when tasks are created at the first time
> b. Task1, task2, Task3 s are queued in Task Starter
> c. When all tasks in a group is ready, tasks are submitted
> d. When tasks start running, task status is updated in Task Manager
> e. Evaluator 3 failed
> f. Driver received failed evaluator event and report it to Evaluator Manager
> g. Task Manager update task status to set task3 as failed
> h. Driver send message to task1 and task2 to stop them and update task status in Task Manager
> i. Driver request a new evaluator3’ for failed evaluator and submit a new context3’ for it and add a new task3’ to the queue
> j. Driver recreate task1’ and task2’ with existing context1 and context2 add them to the queue
> k. When all the new tasks in the communication group are ready, start tasks as in step c.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)