MENG DING commented on YARN-1197:

[~grey], NM will persist the resource decrease in level DB when it receives the 
decrease message, so if it fails and is restarted, it can recover the correct 
container size. In the case of network failure, the decrease message will be 
lost, but it is the same with all other messages in the response (e.g., 
containers to clean up/remove). In practice, I don't think this is a serious 
problem, as we assume by the time a user issues the resource decrease request 
for a container, that container should have already given up the amount of 

Let me know if you have any thoughts or ideas.

> 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