You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2016/03/23 03:57:25 UTC

[jira] [Updated] (TEZ-3161) Allow task to report different kinds of errors - fatal / kill

     [ https://issues.apache.org/jira/browse/TEZ-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Seth updated TEZ-3161:
--------------------------------
    Attachment: TEZ-3161.1.txt

First iteration of the patch. Allows a failure to be marked as FATAL/NON-FATAL and allows a task to be killed from the umbilical.

[~rajesh.balamohan], [~hitesh] - please review.

> Allow task to report different kinds of errors - fatal / kill
> -------------------------------------------------------------
>
>                 Key: TEZ-3161
>                 URL: https://issues.apache.org/jira/browse/TEZ-3161
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>         Attachments: TEZ-3161.1.txt
>
>
> In some cases, task failures will be the same across all attempts - e.g. exceeding memory utilization on an operation. In this case, there's no point in running another attempt of the same task.
> There's other cases where a task may want to mark itself as KILLED - i.e. a temporary error. An example of this is pipelined shuffle.
> Tez should allow both operations.
> cc [~vikram.dixit], [~rajesh.balamohan]



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