tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsuyoshi Ozawa (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEZ-3128) Avoid stopping containers on the AM shutdown thread
Date Fri, 26 Feb 2016 14:28:18 GMT

     [ https://issues.apache.org/jira/browse/TEZ-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tsuyoshi Ozawa updated TEZ-3128:
--------------------------------
    Attachment: TEZ-3128.003.patch

Sounds good idea. I also confirmed that {{YarnTaskSchedulerService#initiateStop()}} releases
all {{heldContainers}}, and {{YarnTaskSchedulerService#shutdown()}} stops all {{delayedContainers}}
with async client. We don't need to release them in TezContainerLauncherImpl. 

> 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, TEZ-3128.003.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)

Mime
View raw message