Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 29 Oct 2014 21:49:34 +0000 (UTC)
From: "Anubhav Dhoot (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12751528.1414619369000.367033.1414619374384@Atlassian.JIRA>
In-Reply-To: <JIRA.12751528.1414619369000@Atlassian.JIRA>
References: <JIRA.12751528.1414619369000@Atlassian.JIRA>
 <JIRA.12751528.1414619369488@arcas>
Subject: [jira] [Created] (YARN-2773) ReservationSystem's use of Queue names
 vs paths is inconsistent for CapacityReservationSystem and
 FairReservationSystem
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)