MENG DING commented on YARN-1197:

One option to consider is to let NM confirm back with RM when it is done 
decreasing the container size. If RM doesn't receive confirmation from NM, it 
will keep sending the decrease message to NM during heartbeat. This is only for 
the purpose of resource enforcement. From scheduling point of view, as soon as 
the decrease request is approved in RM, it takes effect immediately. 

I am not sure if this is worth the effort.

> 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.2015.06.24.pdf, 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

Reply via email to