[
https://issues.apache.org/jira/browse/TEZ-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14028091#comment-14028091
]
Cheolsoo Park commented on TEZ-1117:
------------------------------------
[~bikassaha], [~rohini], I am late to the party here. But this is causing hell
lot of confusion at Netflix too.
{quote}
I can see supporting the thing that you are not asking for Which is
terminating the session when a dag fails. So if a pipeline of dags is being
submitted to the session then the session fails if a member of that pipeline
fails. So a session maps to a pipeline. Not an intended use case for sessions
but not that far off.
{quote}
With this change, failed Pig jobs(scripts) will be labeled as FAILED in RM. Am
I reading this correctly? If that's the case, I am satisfied.
{quote}
Btw, in which cases does Pig need to create a pipeline of dags and submit them
instead of just creating a single DAG? Is there something we can do in Tez to
make that work? What kind of dependency are we not able to express?
{quote}
MergeJoin (PIG-3647) is only one example that is implemented as disjoint DAGs.
[~daijy] should be able to fill you in with details.
> 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)
