[
https://issues.apache.org/jira/browse/TEZ-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716883#comment-14716883
]
Hitesh Shah commented on TEZ-2745:
----------------------------------
bq. Do we currently support running a DAG in an AM where the previous DAG
failed ? Don't we fail the application right now ?
In a session, if a dag fails, this just means that a dag failed - it does not
cause the application to shutdown unless there is an internal error or "Error"
thrown. For non-sessions, a dag failure maps to app failure.
OutOfMemory is an Error not an Exception so would cause an AM shutdown. I
believe we only catch Exception and not Throwable/Error.
> ClassNotFoundException of user code should fail dag
> ---------------------------------------------------
>
> Key: TEZ-2745
> URL: https://issues.apache.org/jira/browse/TEZ-2745
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0, 0.5.4, 0.6.2, 0.8.0-alpha
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Attachments: TEZ-2745-1.patch, TEZ-2745-2.patch
>
>
> This ClassNotFoundException is not captured now. The current behavior is AM
> crashed and relaunched again until max app attempt is reached.
> Here's user code used in AM:
> * EdgeManager
> * VertexManager
> * InputInitializer
> * OutputCommitter
> * Other user pluggable components (like DAGScheduler, HistoryServiceLogging
> etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
