Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 17 Jun 2015 21:57:01 +0000 (UTC)
From: "Xuan Gong (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12634509.1362006332000.102145.1434578221185@Atlassian.JIRA>
In-Reply-To: <JIRA.12634509.1362006332000@Atlassian.JIRA>
References: <JIRA.12634509.1362006332000@Atlassian.JIRA>
 <JIRA.12634509.1362006332804@arcas>
Subject: [jira] [Updated] (YARN-433) When RM is catching up with node
 updates then it should not expire acquired containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xuan Gong updated YARN-433:
---------------------------
    Attachment: YARN-433.2.patch

Fix the testcase failure

> When RM is catching up with node updates then it should not expire acquired containers
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-433
>                 URL: https://issues.apache.org/jira/browse/YARN-433
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Bikas Saha
>            Assignee: Xuan Gong
>         Attachments: YARN-433.1.patch, YARN-433.2.patch
>
>
> RM expires containers that are not launched within some time of being allocated. The default is 10mins. When an RM is not keeping up with node updates then it may not be aware of new launched containers. If the expire thread fires for such containers then the RM can expire them even though they may have launched.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)