[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784803#comment-13784803
]
Wangda Tan commented on YARN-1197:
----------------------------------
Method mentioned by [~sandyr] can solve "cheating" problem in AM side. AM
doesn't need tell RM to decrease container size at all, just tell NM, and let
NM telling RM by heartbeat, the only problem is order of second latency to
decrease in scheduler side, shouldn't be a big problem.
And the race problem mentioned by [~bikassaha], I think it should be
reasonable, when an AM request for more resource on a container, it never know
when RM will return it back. So AM may need to use the smaller resource to
launch container, this is not harmful to either scheduler or NM (use less
resource is not a problem). After sometime, AM will get allocated resource, it
can tell NM and child process to increase memory quota. Do you agree about this?
> 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)
