Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 5 Nov 2013 14:05:22 +0000 (UTC)
From: "Wangda Tan (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12668437.1379062315994.22632.1383660322252@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=13813933#comment-13813933 ] 

Wangda Tan commented on YARN-1197:
----------------------------------

[~bikassaha]
Actually I was on half way of implementing these and stopped by other works. :-/

For putting increasing request to ResourceRequest,
I agree, I really spent some time (the half-baked scheduler supporting increase) to prove putting increasing request to resource request is NOT good, even if you mentioned it before :(. The original reason I put increasing request to ResourceRequest because in literally speaking, the increasing request is another form of "resource request", it also ask for more resource, the only difference is increasing request add a restriction on the request.
But in real YARN's implementation, it's problematic to make it being part of resource request, I need to handle increasing cases everywhere in RM. I think making it a new member in AllocateRequest is cleaner solution, but potentially, it will cause more interfaces/implements changes (like SchedulerApplication, YARNScheduler, etc.). I'll continue look at it before starting write code.

I also agree for you comments for improving representation of ChangeContainerResourceResponse and the missed ResourceIncreaseContextProto in AllocateResponse. I'll add my design proposal for handle new resource in monitoring module.

Again, your comments are really helpful, hope to get your more ideas :)


> 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
>            Assignee: Wangda Tan
>         Attachments: yarn-1197-v2.pdf, yarn-1197-v3.pdf, 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)