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-1345) Throw proper exceptions in IMRU Task
Date Thu, 19 May 2016 18:25:12 GMT

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

Julia commented on REEF-1345:
-----------------------------

I would like to add a big try/catch in IMRU call() to catch exceptions. Except group communication
error that may caused by the chained effect of an evaluate failure, shall we treat the rest
as IMRUAppException or IMRUSystemException? 
Theoretically once IMRU/REEF code are tested, we can assume no error from REEF code. After
filtering known exceptions, I would think the rest should be IMRUAppException. What do you
think? 

> Throw proper exceptions in IMRU Task
> ------------------------------------
>
>                 Key: REEF-1345
>                 URL: https://issues.apache.org/jira/browse/REEF-1345
>             Project: REEF
>          Issue Type: Task
>            Reporter: Julia
>              Labels: FT
>
> For IMRU fault tolerant, we need to identify where to throw proper exceptions with error
messages in places where exception may happen. It includes: 
> TaskFailByCommunication - if there is any error caused by group communication, typical
case is when a task is not able to get messages from its children, this exception should be
thrown .
> TaskFiledByAppError - catch possible application error and throw the corresponding excretions
in those cases. 
> TaskFailedBySystem - any possible system error that could crash the task such as memory,
hard disk, file access, network, etc. 



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

Mime
View raw message