[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624261#action_12624261
]
Vivek Ratan commented on HADOOP-3698:
-------------------------------------
my earlier comments were not quite right. Hemanth's point is valid: there is
some queue configuration that is generic across all queues. This includes queue
names and ACLs, for now. Then there is queue configuration that is different
for different schedulers. We should put these two in separate files, though
they're tied together by queue names, which need to be common across both.
Should the generic queue config be in resource-manager-conf or in
hadoop-default/hadoop-site? Part of the reason for keeping queue-specific stuff
in a separate file was to isolate changes to haddop-default, while we figure
out a more generic way to do queue config (for which HADOOP-3579 was opened).
That reasoning still sounds valid, so the generic queue config stuff should be
in resource-manager-conf till we resolve 3579.
> 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.
