[
https://issues.apache.org/jira/browse/TEZ-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154783#comment-15154783
]
Hitesh Shah commented on TEZ-3128:
----------------------------------
This is done to release containers faster before other services such as ATS are
shutdown which can take a long time. But yes, we need to figure out how to
short-circuit the release if the NM cannot be communicated. Does it make sense
to override the timeouts just for this shutdown phase instead of trying to
avoid stopping them ?
> 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
>
> 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)
