[
https://issues.apache.org/jira/browse/TEZ-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255474#comment-14255474
]
Jeff Zhang commented on TEZ-1843:
---------------------------------
[~hitesh], First I think we should make user understand what the
YarnApplicationStatus mean. IMO, that should mean the final status of this Tez
Application rather than status of any dags. Because there may be multiple dags
in one TezSession, we can't build 1-to-1 relationship between DAG and Tez
Application. So I think if the session is killed when a dag is not running,
that means Tez Application has already done its work and user want to stop it,
it should be normal behavior which should result in SUCCEEDED. While if the
session is shut down when a dag is running. That means user want to interrupt
the Tez Application which resulting in KILLED make more sense.
BTW. I think finally we should encourage user to use the tez-ui to rather than
the yarn ui.
> AM should go to KILLED state when it is killed in RUNNING state
> ---------------------------------------------------------------
>
> Key: TEZ-1843
> URL: https://issues.apache.org/jira/browse/TEZ-1843
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Attachments: TEZ-1843.patch
>
>
> Currently, AM will go to SUCCEEDED state when it is killed in RUNNING state,
> the yarn application also show SUCCEEDED state. But it should go to KILLED
> state instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
