[
https://issues.apache.org/jira/browse/MAPREDUCE-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742804#action_12742804
]
Hemanth Yamijala commented on MAPREDUCE-853:
--------------------------------------------
In summary, the following three areas would be impacted by this change:
- APIs in JobClient (public), JobSubmissionProtocol and QueueManager
- Configuration in mapred-queues.xml and mapred-site.xml
- UI - the hadoop queue family of commands in the CLI and the Scheduling
information shown in the Jobtracker's web UI and Queue details pages.
It is a goal to be able to keep this feature backwards compatible. So sites not
interested in hierarchical queues, but using the current single level of queues
should be able to continue to function as before.
To keep details manageable and not confuse with the high level picture, I will
add tasks under this JIRA for each of these areas.
> Support a hierarchy of queues in the Map/Reduce framework
> ---------------------------------------------------------
>
> Key: MAPREDUCE-853
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-853
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: jobtracker
> Reporter: Hemanth Yamijala
> Fix For: 0.21.0
>
>
> In MAPREDUCE-824, we proposed introducing a hierarchy of queues in the
> capacity scheduler. Currently, the M/R framework provides the notion of job
> queues and handles some functionality related to queues in a
> scheduler-agnostic manner. This functionality includes:
> - Managing the list of ACLs for queues
> - Managing the run state of queues - running or stopped
> - Displaying scheduling information about queues in the jobtracker web UI and
> job client CLI
> - Displaying list of jobs in a queue in the jobtracker web UI and job client
> CLI
> - Providing APIs for list queues and queue information in JobClient.
> Since it would be beneficial to extend this functionality to hierarchical
> queues, this JIRA is proposing introducing the concept into the map/reduce
> framework as well. We could treat this as an umbrella JIRA and file
> additional tasks for each of the changes involved, sticking to the high level
> approach in this JIRA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
