[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587168#comment-14587168
]
Sandy Ryza commented on YARN-1197:
----------------------------------
bq. If you consider all now/future optimizations, such as continous-scheduling
/ scheduler make decision at same AM-RM heart-beat. (b) needs one more NM-RM
heart-beat interval. I agree with you, it could be hundreds of milli-seconds
(a) vs. multi-seconds (b). when the cluster is idle.
To clarify: with proper tuning, we can currently get low hundreds of
milliseconds without adding any new scheduler features. With the new scheduler
feature I'm imagining, we'd only be limited by the RPC + scheduler time, so we
could get 10s of milliseconds with proper tuning.
> 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)
