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

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

Markus Weimer commented on REEF-1345:
-------------------------------------

I got confused about the purpose of this JIRA. I thought this was about defining the right
exceptions to throw in case of application, system and communications error? How to detect
the communications error is a different issue. On that, I agree with [~dkm2110], the network
layer needs to throw different exceptions depending on whether or not an issue is transient.

> 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