[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783708#comment-13783708
]
Bikas Saha commented on YARN-1197:
----------------------------------
Still thinking through the RM-NM interactions. The request for change should
probably be a new object that is basically a map of (containerId, Resource)
where Resource is new value for the existing containerId. Not quite sure how we
would use the new container token for a running container since its only used
in start container.
If we wait for RM to sync with NM about the increased resources then it might
be too slow since this happens on a heartbeat and the heartbeat interval can be
in the order of seconds. An alternative would be a new NM API to allow AM's to
increase resources and this would be signed with new container token. But this
would burden the AMs by requiring them to make that additional call.
There could be a race between a new container token coming in with increased
resources for an acquired container and the old container token being used by
the NMClient to launch the container (in case the AM decides to launch the
smaller container while it was waiting for an increase).
> 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)
