You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Anubhav Dhoot (JIRA)" <ji...@apache.org> on 2014/10/29 22:49:34 UTC

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

Anubhav Dhoot created YARN-2773:
-----------------------------------

             Summary: 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)