[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624052#action_12624052
]
Hemanth Yamijala commented on HADOOP-3698:
------------------------------------------
There seems to be a consensus that managing ACLs should be with the JobTracker.
This is Option 1 which I've mentioned above. I'm OK taking this route.
Like I mentioned in that option, this would mean that queue configuration would
be split in two places
- the generic part (queue names and ACLs, for now)
- scheduler specific part
The simplest way of mapping the generic configuration with scheduler specific
one is to link them using the queue name in some manner.
In HADOOP-3479, we introduced a {{resource-manager-conf.xml}} and a
{{ResourceManagerConf}} class where queues and their properties can be
specified. For e.g. queue properties specific to the scheduler in HADOOP-3445,
are defined in this file, and read by {{ResourceManagerConf}}.
Considering these, I think we have two options regarding where to specify
queues, and scheduler specific queue configuration:
- Continue to use {{resource-manager-conf.xml}} and the {{ResourceManagerConf}}
class. All implementations of schedulers can use this to get list of queues and
any other common properties that are applicable to queues. The HADOOP-3445
scheduler can continue to use {{resource-manager-conf.xml}} to store additional
configuration it needs.
- Move the configuration of the list of queues, and ACLs to {{hadoop-default}}
or {{hadoop-site}} (using the same format as defined in HADOOP-3479), and have
{{resource-manager-conf.xml}} to store configuration specific to HADOOP-3445.
To reflect the generic nature of queues, it seems better to take the second
option. But I am open to comments.
> 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.
