You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2016/05/18 15:33:12 UTC
[jira] [Commented] (REEF-1392) Adding IObserver for
IMRU tasks
[ https://issues.apache.org/jira/browse/REEF-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289157#comment-15289157 ]
Markus Weimer commented on REEF-1392:
-------------------------------------
{quote}
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.
{quote}
This seems problematic. Why throw an exception here, if it is a supported feature? Wouldn't we want the tasks to finish their current iteration and then terminate them?
> 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)