[
https://issues.apache.org/jira/browse/YARN-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subramaniam Krishnan updated YARN-1707:
---------------------------------------
Attachment: YARN-1707.7.patch
Thanks [~jianhe] for your comments. I am updating a patch that has the
following fixes:
* renamed dyQConf/sesConf to entitlement
* userLimit be reinitialized in ReservationQueue/PlanQueue
* Indendation fixed
* Renamed SchedulerConfigEditException to SchedulerDynamicEditException
* Consistently used showReservationsAsQueues for both method as well as the
flag
The newly parsed queues will have the maxApps* as
CapacityScheduler#reinitialize() invokes parseQueues() which is where they are
updated.
> 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.5.patch, YARN-1707.6.patch, YARN-1707.7.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
(v6.3.4#6332)
