[
https://issues.apache.org/jira/browse/YARN-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793017#comment-13793017
]
Sandy Ryza commented on YARN-1122:
----------------------------------
This was fixed by YARN-1236, closing this as duplicate.
> 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 was sent by Atlassian JIRA
(v6.1#6144)
