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 Wed, 18 May 2016 01:34:12 GMT

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

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

We have two options to to tell driver from task for the error. 
* One is using message. In this way, all the exceptions can use the same exception class like
IMRUSystemException. Driver side will get teh message from IFailedTask to see what happend.
* We can also define different exception types, like
   IMRUAppException
   IMRUSystemException
   IMRUGroupCommunicationException
 Driver side can get exception type from IFailedTask to check what kind of error it is. 

Either way would work. 
Any opinion? 

> 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