Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Wed, 18 May 2016 15:02:12 +0000 (UTC)
From: "Markus Weimer (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12960453.1461180892000.224493.1463583732833@Atlassian.JIRA>
In-Reply-To: <JIRA.12960453.1461180892000@Atlassian.JIRA>
References: <JIRA.12960453.1461180892000@Atlassian.JIRA> <JIRA.12960453.1461180892888@arcas>
Subject: [jira] [Commented] (REEF-1345) Throw proper exceptions in IMRU Task
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 18 May 2016 15:02:15 -0000


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

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

I'm in favor of using {{Exception}}s, as they convey the stack trace in addition to the message.

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