Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 3 Oct 2013 22:52:43 +0000 (UTC)
From: "Alejandro Abdelnur (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12668437.1379062315994.9703.1380840763490@arcas>
In-Reply-To: <JIRA.12668437.1379062315994@arcas>
References: <JIRA.12668437.1379062315994@arcas>
Subject: [jira] [Commented] (YARN-1197) Support changing resources of an
 allocated container
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785628#comment-13785628 ] 

Alejandro Abdelnur commented on YARN-1197:
------------------------------------------

Bikas, yep, there is a race condition the AM->RM->NM for decreasing. At least in the FS due to continuous scheduling (YARN-1010) because the RM could allocate the freed space to an AM before the NM heartbeats and gets the info. This does not happen if allocations are tied to the corresponding NM heartbeating. Thanks.

> Support changing resources of an allocated container
> ----------------------------------------------------
>
>                 Key: YARN-1197
>                 URL: https://issues.apache.org/jira/browse/YARN-1197
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: api, nodemanager, resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Wangda Tan
>         Attachments: yarn-1197.pdf
>
>
> Currently, YARN cannot support merge several containers in one node to a big container, which can make us incrementally ask resources, merge them to a bigger one, and launch our processes. The user scenario is described in the comments.


--
This message was sent by Atlassian JIRA
(v6.1#6144)