[
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623942#action_12623942
]
Vivek Ratan commented on HADOOP-3698:
-------------------------------------
bq. Thinking bit more about this, I am wondering where the responsibility of
managing ACLs should be. There seem to be two choices: ...
I think it should be with the JobTracker. Queues are first-class citizens
across the system. JT's submitJob() should look at access control - the job
shouldn't even reach the scheduler unless it passes access control. Agree with
Owen that we don't need Schedulers to deal with security.
It's OK for both the JT and Schedulers to read queue-based information. Both
can make use of the ResourceManagerConf class.
> 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.
