Carlo Curino commented on YARN-1707:

[~jianhe] that is expected. As I was saying in one of the [early comments | 
 we are cutting YARN-1051 into several smaller patches for ease of reviewing, 
but we are trying to make each patch work as standalone (too many dependencies, 
and a bit of a waste of time, 
as they will not be valuable independently). So the fact that doesn't compile 
is expected. We mark them as patch available to signal they are ready to be 

[~wangda]: we have implemented the getDisplayName alternative I mentioned 
above, and we are in the process of testing it. We will post an updated patch 
soon (again not a stand-alone one necessarily).

Thanks again to both of you for quick rounds of review and insightful comments.

> Making the CapacityScheduler more dynamic
> -----------------------------------------
>                 Key: YARN-1707
>                 URL: https://issues.apache.org/jira/browse/YARN-1707
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>              Labels: capacity-scheduler
>         Attachments: YARN-1707.2.patch, YARN-1707.3.patch, YARN-1707.4.patch, 
> YARN-1707.patch
> The CapacityScheduler is a rather static at the moment, and refreshqueue 
> provides a rather heavy-handed way to reconfigure it. Moving towards 
> long-running services (tracked in YARN-896) and to enable more advanced 
> admission control and resource parcelling we need to make the 
> CapacityScheduler more dynamic. This is instrumental to the umbrella jira 
> YARN-1051.
> Concretely this require the following changes:
> * create queues dynamically
> * destroy queues dynamically
> * dynamically change queue parameters (e.g., capacity) 
> * modify refreshqueue validation to enforce sum(child.getCapacity())<= 100% 
> instead of ==100%
> We limit this to LeafQueues. 

This message was sent by Atlassian JIRA

Reply via email to