hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1236) FairScheduler setting queue name in RMApp is not working
Date Thu, 03 Oct 2013 23:38:43 GMT

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

Hudson commented on YARN-1236:

SUCCESS: Integrated in Hadoop-trunk-Commit #4530 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4530/])
YARN-1236. FairScheduler setting queue name in RMApp is not working. (Sandy Ryza) (sandy:
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java
* /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java

> FairScheduler setting queue name in RMApp is not working 
> ---------------------------------------------------------
>                 Key: YARN-1236
>                 URL: https://issues.apache.org/jira/browse/YARN-1236
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.1.0-beta
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>             Fix For: 2.1.2-beta
>         Attachments: YARN-1236.patch
> The fair scheduler sometimes picks a different queue than the one an application was
submitted to, such as when user-as-default-queue is turned on.  It needs to update the queue
name in the RMApp so that this choice will be reflected in the UI.
> This isn't working because the scheduler is looking up the RMApp by application attempt
id instead of app id and failing to find it.

This message was sent by Atlassian JIRA

View raw message