MENG DING updated YARN-1197:
    Attachment: YARN-1197_Design.2015.08.21.pdf

The NodeManager side of the implementation has been completed. Many thanks to 
[~jianhe] and [~leftnoteasy] for the review and valuable comments. There have 
been quite a few design changes along the way (for the better!), and I have 
updated the design doc accordingly. The main changes include:

* Getting rid of the {{IncreasedContainerProto}} and 
{{DecreasedContainerProto}}, and just use the existing {{ContainerProto}}.
* Container resource is now updated synchronously in NM as the whole process is 
fairly light weighted. This greatly simplifies the logic. The 
{{ContainerManager#increaseContainersResource}} call is now a blocking call, 
and a success return of this function means that the increase is completed in 
NM, and no further container status checking is required by AM. 
* Container resource increase is synchronized with NM-RM registration to handle 
the race condition of RM restarts while container resource increase is in 

> 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.2015.07.07.pdf, 
> YARN-1197_Design.2015.08.21.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