[
https://issues.apache.org/jira/browse/MAPREDUCE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated MAPREDUCE-824:
---------------------------------------
Attachment: MAPREDUCE-824-6.patch
Attached patch incorporates all comments I raised, except the following:
- JobQueue.removeWaitingJob is used by JobInitializationPoller. Hence, retained
the access level as package private.
- I also did not fold methods in JobQueue and JobQueuesManager since most
seemed to be used at more than one place.
In addition to the comments, Rahul and I also found and fixed a bug in
getMaxCapacity() and changed the default value of the same to -1 in the
capacity-scheduler.xml.template.
Rahul, can you please take a look at the changes and make sure you are fine
with them ?
> Support a hierarchy of queues in the capacity scheduler
> -------------------------------------------------------
>
> Key: MAPREDUCE-824
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-824
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: contrib/capacity-sched
> Reporter: Hemanth Yamijala
> Attachments: HADOOP-824-1.patch, HADOOP-824-2.patch,
> HADOOP-824-3.patch, HADOOP-824-4.patch, HADOOP-824-5.patch,
> MAPREDUCE-824-6.patch
>
>
> Currently in Capacity Scheduler, cluster capacity is divided among the queues
> based on the queue capacity. These queues typically represent an organization
> and the capacity of the queue represents the capacity the organization is
> entitled to. Most organizations are large and need to divide their capacity
> among sub-organizations they have. Or they may want to divide the capacity
> based on a category or type of jobs they run. This JIRA covers the
> requirements and other details to provide the above feature.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
