[ 
https://issues.apache.org/jira/browse/HADOOP-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623741#action_12623741
 ] 

Hemanth Yamijala commented on HADOOP-3698:
------------------------------------------

Thinking bit more about this, I am wondering where the responsibility of 
managing ACLs should be. There seem to be two choices:
- In the JobTracker: In this approach, the jobtracker manages queues which will 
have common configuration like names, ACLs (possibly the only two common ones 
for now). In addition, different schedulers could have specific properties for 
queues - for e.g. HADOOP-3445 has capacities, user limits etc. There should be 
a way to associate the queues defined in the job tracker with their properties 
in a scheduler.
- In the scheduler: In this approach, we treat queues as being related to 
schedulers. The jobtracker would delegate the verification of ACLs to the 
scheduler instance it is configured with. This approach means that something 
like the {{verifyAccess}} API, along with the {{QueueOperation}} enum would be 
defined in the {{TaskScheduler}} interface. Since different schedulers may want 
to benefit from the same verification mechanism, we could build the 
verification logic as a separate utility class.

I am thinking that the second option is better. Logically queues do seem to be 
related closer to schedulers. 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.

Reply via email to