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/12/09 22:25:58 UTC
[jira] [Assigned] (REEF-1492) On IMRU recovery: if
ResultHandler.Dispose() throws exception, IMRU Driver hangs.
[ https://issues.apache.org/jira/browse/REEF-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julia reassigned REEF-1492:
---------------------------
Assignee: Julia
> On IMRU recovery: if ResultHandler.Dispose() throws exception, IMRU Driver hangs.
> ---------------------------------------------------------------------------------
>
> Key: REEF-1492
> URL: https://issues.apache.org/jira/browse/REEF-1492
> Project: REEF
> Issue Type: Bug
> Components: REEF
> Reporter: Andrey
> Assignee: Julia
> Labels: FT
>
> IMRU scenario:
> - one of the map tasks fails
> - Driver triggers shutdown on all tasks
> - UpdateTaskHost on shutdown is calling ResultHandler.Dispose()
> - resulthandler (in my case WriteResultHandler) throws exeption because there are no results (Update function was never executed)
> There are couple questions here:
> - WriteResulthandler should handle [no results] situation more gracefully, especially on Dispose()
> Probably logic of copy file should be moved from Dispose() to HandleResult() function.
> - UpdateTaskHost should handle exceptions from Dispose() call....result handler can be provided by client, so code can throw.
> In case of Dispose() failure the UpdateTaskHost should probably trigger non-recoverable failure, which in turn triggers Driver failure (right now driver hangs)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)