hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5295) YARN queue-mappings to check Queue is present before submitting job
Date Thu, 30 Jun 2016 09:00:21 GMT

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

Sunil G commented on YARN-5295:

Hi [~Prabhu Joseph]

In YARN-3635, a new {{PlacementManager}} is added. It takes care of queue mappings in general
across schedulers. 
Code snippet from {{CS#getUserGroupMappingPlacementRule}},
         if (queue == null || !(queue instanceof LeafQueue)) {
          throw new IOException("mapping contains invalid or non-leaf queue "
             + mappingQueue);
While loading queue-mappings from conf, a validation is done for *non-existent* and *non-leafQueues*.
And this {{QueueMapping}} is used in {{PlacementManager}} to do the placement activity in

But this is not present in branch2.7 against which you raised this ticket. [~leftnoteasy],
could we backport YARN-3635 to branch-2.7. Its present in branch-2.8 already. 

> 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message