Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Sun, 28 Feb 2016 10:55:18 +0000 (UTC)
From: "Tsuyoshi Ozawa (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12940619.1455911728000.167108.1456656918052@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=15171001#comment-15171001 ] 

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

Thanks [~sseth] and [~jlowe] for the review and pulling it into branch-0.7.

> 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
>             Fix For: 0.7.1, 0.8.3
>
>         Attachments: TEZ-3128.001.patch, TEZ-3128.002.patch, TEZ-3128.003.patch, TEZ-3128.004.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)