Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 29 Jun 2015 16:04:09 +0000 (UTC)
From: "Lei Guo (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12668437.1379062315000.44658.1435593849922@Atlassian.JIRA>
In-Reply-To: <JIRA.12668437.1379062315000@Atlassian.JIRA>
References: <JIRA.12668437.1379062315000@Atlassian.JIRA>
 <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=14605807#comment-14605807 ] 

Lei Guo commented on YARN-1197:
-------------------------------

[~mding], for the decrease flow via NodeHeartbeatResponseProto to notify NM, how we handle the case on network/NM failure?

> 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 old-design-docs-patches-for-reference.zip, YARN-1197_Design.2015.06.24.pdf, YARN-1197_Design.pdf
>
>
> The current YARN resource management logic assumes resource allocated to a container is fixed during the lifetime of it. When users want to change a resource 
> of an allocated container the only way is releasing it and allocating a new container with expected size.
> Allowing run-time changing resources of an allocated container will give us better control of resource usage in application side


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