[
https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587072#comment-14587072
]
Sandy Ryza commented on YARN-1197:
----------------------------------
bq. RM still needs to wait for an acknowledgement from NM to confirm that the
increase is done before sending out response to AM. This will take two
heartbeat cycles, but this is not much worse than giving out a token to AM
first, and then letting AM initiating the increase.
I would argue that waiting for an NM-RM heartbeat is much worse than waiting
for an AM-RM heartbeat. With continuous scheduling, the RM can make decisions
in millisecond time, and the AM can regulate its heartbeats according to the
application's needs to get fast responses. If an NM-RM heartbeat is involved,
the application is at the mercy of the cluster settings, which should be in the
multi-second range for large clusters.
> 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)
