reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <>
Subject [jira] [Commented] (REEF-1335) Create State Machine for IMRU fault tolerance
Date Tue, 19 Apr 2016 22:43:25 GMT


Markus Weimer commented on REEF-1335:

Are we going to make sure via locks that we are only in one of the handlers (different FailedTask,
FailedEvaluator, ActiveContext handlers etc.) at a time.

I don't think we need that. But whenever the state on one of the state machines changes, we
should acquire a lock on that state machine object. That's how we solved similar issues in
the REEF Driver.

> Create State Machine for IMRU fault tolerance
> ---------------------------------------------
>                 Key: REEF-1335
>                 URL:
>             Project: REEF
>          Issue Type: Task
>          Components: IMRU, REEF.NET
>            Reporter: Julia
>            Assignee: Julia
>              Labels: FT
>         Attachments: REEF Fault Tolerant Technical design.docx
> To Support fault tolerant, we would like to use state machine to control the system state
> After driver is created, it will start from request evaluators and submit contexts state;
after all the contexts are ready, it will move to submitting tasks state; when all the tasks
are start running, it moves to tasks running state; when all the tasks are completed, the
state will be changed to tasks completed. If either tasks or evaluators fail, it will change
to shut down state, etc. 
> Here are the proposed system states:
> * WaitingForEvaluator,
> * SubmitingTasks,
> * TasksRunning,
> * TasksCompleted,
> * ShutingDown,
> * Fail
> Here are the event that may trigger the state change:
> * AllContextsAreReady,
> * AllTasksAreRunning,
> * AllTasksAreCompleted,
> * FailedTask,
> * FailedEvaluator,
> * NotRecoverable,
> * Recover

This message was sent by Atlassian JIRA

View raw message