[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-1197:
-----------------------------
Attachment: yarn-1197-v4.pdf
I updated design doc mainly based on [~bikassaha] latest comment,
I left "Add implementation to NM to support changing resource isolation
limitation of a container" blank in design doc. From my understanding,
currently, LCE doesn't do any memory isolation (right?), it will setup CPU
share when it setup a container. Currently I don't have whole picture of these
component, solutions I can think are,
1) Because this is a soft limitation, we just don't do anything in LCE side
2) Create a new interface in ContainerExecutor, which can update resource of a
container
3) Disable increase/shrink when LCE is selected
Hope to get your more opinions on this and design doc.
> 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)
