Mailing-List: contact issues-help@tez.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.apache.org
Date: Fri, 26 Feb 2016 05:44:18 +0000 (UTC)
From: "Siddharth Seth (JIRA)" <jira@apache.org>
To: issues@tez.apache.org
Message-ID: <JIRA.12940619.1455911728000.152372.1456465458065@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=15168481#comment-15168481 ] 

Siddharth Seth commented on TEZ-3128:
-------------------------------------

[~ozawa] - looking at the scheduler, we already release all held containers as part of the shutdown process (way before we unregister from the RM). Given that, avoiding the container stop completely would be a better option, and simpler patch.

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