[jira] [Commented] (YARN-2773) ReservationSystem's use of Queue names vs paths is inconsistent for CapacityReservationSystem and FairReservationSystem

["Anubhav Dhoot (JIRA)" <ji...@apache.org>]

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

Anubhav Dhoot commented on YARN-2773:
-------------------------------------

getAdmissionPolicy uses the planQueuePath (fully qualified) while rest of the methods (e.g. getPlanQueueCapacity) uses planQueueName (just leaf queue name). 

> ReservationSystem's use of Queue names vs paths is inconsistent for CapacityReservationSystem and FairReservationSystem  
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2773
>                 URL: https://issues.apache.org/jira/browse/YARN-2773
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>            Reporter: Anubhav Dhoot
>            Priority: Minor
>
> Reservation system requires use the ReservationDefinition to use a queue name to choose which reservation queue is being used. CapacityScheduler does not allow duplicate leaf queue names. Because of this we can refer to a unique leaf queue by simply using its name and not full path (which includes parentName + "."). FairScheduler allows duplicate leaf queue names because of which one needs to refer to the full queue name to identify a queue uniquely. This is inconsistent for the implementation of the AbstractReservationSystem where one implementation of getQueuePath will do conversion (CapacityReservationSystem) while the FairReservationSystem will return the same value back 



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