[
https://issues.apache.org/jira/browse/MAPREDUCE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741192#action_12741192
]
Sreekanth Ramakrishnan commented on MAPREDUCE-824:
--------------------------------------------------
To clarify the above comment was:
{quote}
What would QueueManager.getQueues() give to JobInitializationPoller in
CapacityScheduler.start()
{quote}
The {{JobInitalizationPoller}} acts only on {{JobQueue}} not {{ContainerQueue}}
which is configured by the {{QueueManager}}.
I agree, the future patch would address configuration related changes, but
atleast interim the patch should see to that {{JobInitalizationPoller}} would
get only {{JobQueue}}.
> 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
>
>
> 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.
