[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624228#action_12624228
]
Vivek Ratan commented on HADOOP-3698:
-------------------------------------
bq. Considering these, I think we have two options regarding where to specify
queues, and scheduler specific queue configuration:
I'd favor the first option. Placing all the queue configuration in one file
(resource-manager-conf.xml) makes it easier for someone to configure queues.
They shouldn't care about what configuration is scheduler-specific and what is
not. The individual components (JobTracker, Scheduler) can read whatever they
need from this one file, or rather, from the one class that represents this
file. You don't want this split (each component reading what it wants) to
necessarily show up in the config file. If you move code around later, you'd
end up moving config values between various files, which is not good.
> Implement access control for submitting jobs to queues in the JobTracker
> ------------------------------------------------------------------------
>
> Key: HADOOP-3698
> URL: https://issues.apache.org/jira/browse/HADOOP-3698
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Fix For: 0.19.0
>
>
> HADOOP-3445 implements multiple queues in the JobTracker as part of the new
> resource manager for Hadoop (HADOOP-3421). There needs to be a mechanism to
> control who can submit jobs to a specified queue. This JIRA is for tracking
> the requirements, approach and implementation for the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
