[
https://issues.apache.org/jira/browse/TEZ-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028450#comment-14028450
]
Bikas Saha commented on TEZ-1117:
---------------------------------
A disjoint group of DAG can be submitted as a single DAG since its still a DAG.
We can run a forest of disconnected DAGs. So I would like to understand the use
case.
We could add a config that makes the session fail when a DAG in that session
fails. You can use this setting when submitting a pipeline of jobs but probably
not in your shell/interactive mode (grunt?)
Also what are you thoughts on this comment of mine about using sessions for
your ETL stuff.
bq.The session API is not fire and forget. The DAG cannot be submitted to the
session until the app starts running and accepts the DAG over RPC. Which means
that its stuck on a busy cluster. If we do this then users cannot fire their
Pig scripts and go away. They need to maintain the running console until
resources free up in the cluster at some unbounded time in the future.
> 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)
