hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1122) FairScheduler user-as-default-queue always defaults to 'default'
Date Thu, 29 Aug 2013 16:52:52 GMT

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

Sandy Ryza commented on YARN-1122:

Thanks for taking this up, [~lohit].  Would it be possible to add a test?
> 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

View raw message