[
https://issues.apache.org/jira/browse/TEZ-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254067#comment-14254067
]
Hitesh Shah commented on TEZ-1843:
----------------------------------
[~zjffdu] Thinking on this a bit more, the patch might result in a bit more
confusion. Stopping the session when a dag is not running makes it go to
succeeded but stopping it when a dag is running makes it go to KILLED.
Furthermore, there may be cases where a session has succeeded but killedDags
will be non-zero.
Maybe, it might be better to work on a patch that addresses this jira as well
as TEZ-1117 to get a final overall agreed upon approach.
> 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)
