reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1392) Adding IObserver<ICloseEvent> for IMRU tasks
Date Tue, 24 May 2016 00:53:12 GMT

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

Julia commented on REEF-1392:
-----------------------------

For keeping the state, that is related to check point. We should do it in a separate JIRA.


Basically, we should keep state in regular bases because we have to be prepared for sudden
crash rather than gracefully close anyway. Then when we restart the task again, we should
always read the last good state from some persistent store. 

In IMRU task in particular, what are state shall be kept, where/when to keep it, how to read
it in recovery scenario and coordinate with other tasks, is really another Jira and we should
discuss about those there. 

> Adding IObserver<ICloseEvent> for IMRU tasks
> --------------------------------------------
>
>                 Key: REEF-1392
>                 URL: https://issues.apache.org/jira/browse/REEF-1392
>             Project: REEF
>          Issue Type: Task
>            Reporter: Julia
>            Assignee: Julia
>              Labels: FT
>
> For fault tolerant, IMRU tasks, MapTaskHost and UpdateTaskHost should implement  IObserver<ICloseEvent>.
When they receive ICloseEvent,  it will verify if the closing event is send from driver based
on the message in the event, then trow IMRUTaskException with a define message to inform the
driver it is closed. 
> The  change should be backward compatible. If the the IMRU tasks are not bound to the
task configuration for  TaskConfiguration.OnClose, the event won't be received. 



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

Mime
View raw message