[
https://issues.apache.org/jira/browse/TEZ-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998916#comment-13998916
]
Rohini Palaniswamy commented on TEZ-1117:
-----------------------------------------
Pig script execution is not fire and go away. Pig client stays on till the
script execution is complete and if users are running from commandline they use
screen. If pig client terminates for any reason, it kills the running
applications (MR job or Tez sessions) in its shutdown hook.
I am not asking for session to terminate if one DAG fails. All I am asking is
that when the session terminates after executing all DAGs ( when we shut it
down via TezSession.stop() or it terminates automatically due to timeout
because no new DAGs were submitted and no stop() was called) its Application
FinalStatus show KILLED instead of SUCCEEDED if there was a killed DAG or
FAILED if there was a failed DAG.
{code}
User: rohinip
Name: PigLatin:test.pig
Application Type: TEZ
Application Tags:
State: FINISHED
FinalStatus: SUCCEEDED
Started: 13-May-2014 22:38:58
Elapsed: 14mins, 11sec
Tracking URL: History
Diagnostics:
Session stats:submittedDAGs=1, successfulDAGs=0, failedDAGs=1, killedDAGs=0
{code}
I am fine with the current diagnostics. It is very useful.
> Option to make YARN application failed on dag failure
> -----------------------------------------------------
>
> Key: TEZ-1117
> URL: https://issues.apache.org/jira/browse/TEZ-1117
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rohini Palaniswamy
>
> Can we have an configuration to make the Application status FAILED on
> termination if one of the DAGs fail? It is very confusing for users to see
> the application SUCCEEDED.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
