[ 
https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351384#comment-15351384
 ] 

Sunil G commented on YARN-5295:
-------------------------------

Thanks [~Prabhu Joseph] for the clarification.
Yes, we select a queue and then we do sanity after that. And if sanity check 
(validations) fails for this selected queue, we will reject the app submission. 
In this given scenario, may be a group configuration seems valid and the jira 
is focussing on that point. Got it. +1 for the approach.

Interestingly we need to see how 3rd point is to be handled {{3. is user either 
have ACL Submit_Applications or Administer_Queue of the queue.}}, we may 
possibly relax some ACLs here if we do that. If a user (user *test*) is not 
given permission to queue (queue named *test* in this context), and same user's 
group (group *edw*) has permission in another queue (queue named *platform* in 
this context), I think we have to give preference for user than group. So i 
think current implementation holds good for 3rd point. Thoughts? 

> YARN queue-mappings to check Queue is present before submitting job
> -------------------------------------------------------------------
>
>                 Key: YARN-5295
>                 URL: https://issues.apache.org/jira/browse/YARN-5295
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>    Affects Versions: 2.7.2
>            Reporter: Prabhu Joseph
>
> In yarn Queue-Mappings, Yarn should check if the queue is present before 
> submitting the job. If not present it should go to next mapping available.
> For example if we have
> yarn.scheduler.capacity.queue-mappings=u:%user:%user,g:edw:platform
> and I submit job with user "test" and if there is no "test" queue then it 
> should check the second mapping (g:edw:platform) in the list and if test is 
> part of edw group it should submit job in platform queue.
> Below Sanity checks has to be done for the mapped queue in the list and if it 
> fails then the the next queue mapping has to be chosen, when there is no 
> queue mapping passing the sanity check, only then the application has to be 
> Rejected.
> 1. is queue present
> 2. is queue not a leaf queue
> 3. is user either have ACL Submit_Applications or Administer_Queue of the 
> queue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to