[
https://issues.apache.org/jira/browse/TEZ-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227749#comment-15227749
]
Bikas Saha commented on TEZ-3161:
---------------------------------
Does a fatal error affect the recovery code path? E.g. fatal error got stored
but dag failure did not get stored. What happens in recovery? Should dag fail
after recovery because task fatal error was recovered. Likely yes, but does it
work? Please ignore this comment in case its already covered.
> 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
> Assignee: Siddharth Seth
> Fix For: 0.8.3
>
> Attachments: TEZ-3161.1.txt, TEZ-3161.2.txt, TEZ-3161.3.txt,
> TEZ-3161.4.txt, TEZ-3161.5.txt, TEZ-3161.6.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)
