[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828374#comment-13828374
]
Wangda Tan commented on YARN-1197:
----------------------------------
[~sandyr]
These bunch of code will be hard for review, but I will make and upload a
all-in-one draft patch for early preview before split it. I hope I can finish
the alpha patch during this weekend :-]
I agree you mentioned YARN enforce memory monitoring via ContainersMonitor, I
ask this because I noticed the design doc of YARN-3,
https://issues.apache.org/jira/secure/attachment/12538426/mapreduce-4334-design-doc-v2.txt,
the "Design 2(b)" mentioned "ResoureEnforcer.init()", before create cgroups. I
found this is not done yet, so we can safely update the resource enforce via
update limit of ContainersMonitor now.
> 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-v4.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)
