[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586455#comment-14586455
]
Vinod Kumar Vavilapalli commented on YARN-1197:
-----------------------------------------------
bq. We all agreed that due to the complexity of the current design, it is
worthwhile to revisit the idea of increasing and decreasing container size both
through Resource Manager
+1 for this idea. Letting this go through NodeManager directly adds too much
complexity and difficult to understand semantics for the application writers.
bq. If I understand correctly, this would be considerable hit to performance
[~sandyr], as I understand, going through NM is in fact a worse solution w.r.t
allocation throughput. Going through RM directly is better as the RM will
immediately know that the resource is available for future allocations - the
decrease on the NM can happen offline. The control flow I expect is
- the framework/app decides it doesn't need that many resources anymore. By
this time, the container already should have given up on the physical resources
it doesn't need
- informs the RM about the required decrement
- RM informs NM to resize the container (cgroups etc)
> 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 old-design-docs-patches-for-reference.zip,
> YARN-1197_Design.pdf
>
>
> The current YARN resource management logic assumes resource allocated to a
> container is fixed during the lifetime of it. When users want to change a
> resource
> of an allocated container the only way is releasing it and allocating a new
> container with expected size.
> Allowing run-time changing resources of an allocated container will give us
> better control of resource usage in application side
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
