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/05/10 21:20:12 UTC

[jira] [Commented] (REEF-1345) Throw proper exceptions in IMRU Task

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

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

Here are the exception messages defined in TaskManager:

        internal const string TaskAppError = "TaskAppError";
        internal const string TaskSystemError = "TaskSystemError";
        internal const string TaskGroupCommunicationError = "TaskGroupCommunicationError";
        internal const string TaskEvaluatorError = "TaskEvaluatorError";


> 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)