You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Lohit Vijayarenu (JIRA)" <ji...@apache.org> on 2013/08/29 18:40:53 UTC

[jira] [Updated] (YARN-1122) FairScheduler user-as-default-queue always defaults to 'default'

     [ https://issues.apache.org/jira/browse/YARN-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lohit Vijayarenu updated YARN-1122:
-----------------------------------

    Attachment: YARN-1122.1.patch

Simple patch to fix this. 
                
> FairScheduler user-as-default-queue always defaults to 'default'
> ----------------------------------------------------------------
>
>                 Key: YARN-1122
>                 URL: https://issues.apache.org/jira/browse/YARN-1122
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.0.5-alpha
>            Reporter: Lohit Vijayarenu
>         Attachments: YARN-1122.1.patch
>
>
> By default YARN fairscheduler should use user name as queue name, but we see that in our clusters all jobs were ending up in default queue. Even after picking YARN-333 which is part of trunk, the behavior remains the same. Jobs do end up in right queue, but from UI perspective they are shown as running under default queue. It looks like there is small bug with
> {noformat}
> RMApp rmApp = rmContext.getRMApps().get(applicationAttemptId);
> {noformat}
> which should actually be
> {noformat}
> RMApp rmApp = rmContext.getRMApps().get(applicationAttemptId.getApplicationId());
> {noformat}
> There is also a simple js change needed for filtering of jobs on fairscheduler UI page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira