Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Tue, 23 Feb 2016 00:20:18 +0000 (UTC)
From: "Tsuyoshi Ozawa (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12940619.1455911728000.115855.1456186818073@Atlassian.JIRA>
In-Reply-To: <JIRA.12940619.1455911728000@Atlassian.JIRA>
References: <JIRA.12940619.1455911728000@Atlassian.JIRA>
 <JIRA.12940619.1455911728785@arcas>
Subject: [jira] [Commented] (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:comment-tabpanel&focusedCommentId=15158004#comment-15158004 ] 

Tsuyoshi Ozawa commented on TEZ-3128:
-------------------------------------

[~hitesh] [~sseth] Thank you for pointing.

{quote}
dagappmaster shuts down yarn scheduler service but it does not kill containers on shutdown - just releases them via amrmclient
TezTaskCommunicatorImpl on stop() does nothing to kill containers.
{quote}

Right, that's why I thought the place I fixed was what you mentioned. Could you help me to clarify where to fix?

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