[
https://issues.apache.org/jira/browse/TEZ-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14647056#comment-14647056
]
Jeff Zhang commented on TEZ-2311:
---------------------------------
bq. What kind of problems do you see if we potentially treat
DAGKillRequestEvent summary event as the same as seeing a DAGFinished
SummaryEvent with state KILLED?
It is different when I try to reuse the KilTransition code in the previous
patch, will be no difference when recovering dag to KILLED directly.
Upload new patch
* Fix the grammar typo
* Recover the dag to KILLED directly in all the cases when DAGKillRequestEvent
is seen.
* Move the shutdown code block after the recovering code in
DAGAppMaster#serviceStart
> AM can hang if kill received while recovering from previous attempt
> -------------------------------------------------------------------
>
> Key: TEZ-2311
> URL: https://issues.apache.org/jira/browse/TEZ-2311
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Jason Lowe
> Assignee: Jeff Zhang
> Labels: Recovery
> Attachments: TEZ-2311-1.patch, TEZ-2311-2.patch, TEZ-2311-3.patch,
> TEZ-2311-4.patch, TEZ-2311-5.patch, TEZ-2311-6.patch
>
>
> We saw an instance of a Tez job hanging despite receiving multiple kill
> requests from clients. The AM was recovering from a prior attempt when the
> first kill request arrived.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
