hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wilfred Spiegelenburg (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-1122) FairScheduler user-as-default-queue always defaults to 'default'
Date Sat, 12 Jan 2019 13:13:00 GMT

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

Wilfred Spiegelenburg resolved YARN-1122.
    Resolution: Duplicate

closing old jira as duplicate per comment

> 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
>            Priority: Major
>         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

To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org

View raw message