reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1392) Adding IObserver<ICloseEvent> for IMRU tasks
Date Thu, 19 May 2016 01:30:13 GMT

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

Markus Weimer commented on REEF-1392:
-------------------------------------

Why would it have to be synchronized? The map task "just" needs to be able to restart from
an older iteration number. Maybe we need to add an API for tasks to store their state, indexed
by iteration count? IMRU knows when we enter the next iteration and therefore drop old entries
with certainty.

> 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