Wangda Tan commented on YARN-1197:

Hi [~mding],
I just completed clean up of sub JIRAs. I think some of them are too detailed. 
For example, it will be very hard to split works in 
FiCaSchedulerNode/FiCaSchedulerApp with changes of LeafQueue/ParentQueue. 
Following are JIRAs after cleanup:

YARN-1449, API in NM side to support change container resource.
YARN-1502, API changes in RM side to support change contaienr resource.

YARN-1509, AMRMClient
YARN-1510, NMClient

*NM implementation*
YARN-1643, ContainerMonitor changes in NM

*RM implementation*
YARN-1646, Support change container resource in RM.
YARN-1651, CapacityScheduler side changes.

I unassigned myself from many of these JIRAs, but I still plan to implement 
changes in RM/CS side. For other JIRAs, please feel free to take.

> 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_Design.pdf, mapreduce-project.patch.ver.1, 
> tools-project.patch.ver.1, yarn-1197-scheduler-v1.pdf, yarn-1197-v2.pdf, 
> yarn-1197-v3.pdf, yarn-1197-v4.pdf, yarn-1197-v5.pdf, yarn-1197.pdf, 
> yarn-api-protocol.patch.ver.1, yarn-pb-impl.patch.ver.1, 
> yarn-server-common.patch.ver.1, yarn-server-nodemanager.patch.ver.1, 
> yarn-server-resourcemanager.patch.ver.1
> 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