[
https://issues.apache.org/jira/browse/TEZ-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168481#comment-15168481
]
Siddharth Seth commented on TEZ-3128:
-------------------------------------
[~ozawa] - looking at the scheduler, we already release all held containers as
part of the shutdown process (way before we unregister from the RM). Given
that, avoiding the container stop completely would be a better option, and
simpler patch.
> Avoid stopping containers on the AM shutdown thread
> ---------------------------------------------------
>
> Key: TEZ-3128
> URL: https://issues.apache.org/jira/browse/TEZ-3128
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.0-alpha
> Reporter: Siddharth Seth
> Assignee: Tsuyoshi Ozawa
> Labels: newbie
> Attachments: TEZ-3128.001.patch, TEZ-3128.002.patch, amJstack
>
>
> During an AM shutdown, the TaskCommunicator is also shutdown and it tries to
> stop containers in the shutdown thread itself. This can cause the AM shutdown
> to block if NMs are not available.
> This likely affects 0.7 as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
