[
https://issues.apache.org/jira/browse/YARN-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351450#comment-15351450
]
Prabhu Joseph commented on YARN-5295:
-------------------------------------
Yes, doing Sanity Check 1 and 2 well before in getMappedQueue is suffice to
help administrators to configure a default queue to any user or group in case
of no valid queue mapping. For example, with this fix, Administrators can allow
any new user added and who does not have queue created with same user name can
still be placed in default queue through list of queue mappings
u:%user:%user,u:%user:default
> 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
