Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Fri, 26 Feb 2016 14:28:18 +0000 (UTC)
From: "Tsuyoshi Ozawa (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12940619.1455911728000.156064.1456496898065@Atlassian.JIRA>
In-Reply-To: <JIRA.12940619.1455911728000@Atlassian.JIRA>
References: <JIRA.12940619.1455911728000@Atlassian.JIRA>
 <JIRA.12940619.1455911728785@arcas>
Subject: [jira] [Updated] (TEZ-3128) Avoid stopping containers on the AM
 shutdown thread
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)