[
https://issues.apache.org/jira/browse/TEZ-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639058#comment-14639058
]
Jeff Zhang commented on TEZ-2311:
---------------------------------
[~jlowe] Check your previous comment again and find the root cause. The
scenario is that vertex is killed before its tasks being scheduled which means
there's no recovery log for tasks (that's why you see task's recoveredState is
NEW). and which result in vertex never get feedback from its tasks. Will post
a patch to fix it soon.
> 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
> Labels: Recovery
>
> 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)