[
https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351347#comment-15351347
]
Prabhu Joseph edited comment on YARN-5295 at 6/27/16 4:25 PM:
--------------------------------------------------------------
Hi [~sunilg], Yes, if test queue is present, the application submitted by test
user placed into test queue. But if test queue is not present or if test queue
is not a leaf queue or if test user does not have either Submit_Applications or
Administer_Queue ACL, then the application is rejected. Instead, the
getMappedQueue in CapacityScheduler can do the three sanity checks well before
and return a valid queue that is platform instead of test. (Assuming test user
passes the sanity checks on platform Queue)
Currently the sanity checks are done separately after deciding the queue to be
placed, instead sanity checks can be included in getMappedQueue logic, where
once queue mapping is chosen from the list, the sanity checks can be done and
if it fails, then move to the next queue mapping in the list.
was (Author: prabhu joseph):
Hi [~sunilg], Yes, if test queue is present, the application submitted by test
user placed into test queue. But if test queue is not present or if test queue
is not a leaf queue or if test user does not have either Submit_Applications or
Administer_Queue ACL, then the application is rejected. Instead, the
getMappedQueue in CapacityScheduler can do the three sanity checks and return a
valid queue that is platform instead of test. (Assuming test user passes the
sanity checks on platform Queue)
Currently the sanity checks are done separately after deciding the queue to be
placed, instead sanity checks can be included in getMappedQueue logic, where
once queue mapping is chosen from the list, the sanity checks can be done and
if it fails, then move to the next queue mapping in the list.
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
