hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miklos Szegedi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7139) FairScheduler: finished applications are always restored to default queue
Date Fri, 19 Jan 2018 01:43:00 GMT

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

Miklos Szegedi commented on YARN-7139:

+1. I cannot reproduce the unit test failure.

> FairScheduler: finished applications are always restored to default queue
> -------------------------------------------------------------------------
>                 Key: YARN-7139
>                 URL: https://issues.apache.org/jira/browse/YARN-7139
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.8.1
>            Reporter: Wilfred Spiegelenburg
>            Assignee: Wilfred Spiegelenburg
>            Priority: Major
>         Attachments: YARN-7139.01.patch, YARN-7139.02.patch, YARN-7139.03.patch, YARN-7139.04.patch
> The queue an application gets submitted to is defined by the placement policy in the
FS. The placement policy returns the queue and the application object is updated. When an
application is stored in the state store the application submission context is used which
has not been updated after the placement rules have run. 
> This means that the original queue from the submission is still stored which is the incorrect
queue. On restore we then read back the wrong queue and display the wrong queue in the RM
web UI.
> We should update the submission context after we have run the placement policies to make
sure that we store the correct queue for the application.

This message was sent by Atlassian JIRA

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

View raw message