hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-7586) Application Placement should be done before ACL checks in ResourceManager
Date Sat, 02 Dec 2017 04:53:00 GMT

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

Suma Shivaprasad updated YARN-7586:
    Attachment: YARN-7586.4.patch

Thanks [~sunilg] Attached patch with comments addressed.

RMActiveServiceContext ensures that PlacementManager is no null since is it created during
its construction. This is just a saftey check to make sure its set. Have added an additional
check to log the error and throw an exception if the specified queue is also invalid

> Application Placement should be done before ACL checks in ResourceManager
> -------------------------------------------------------------------------
>                 Key: YARN-7586
>                 URL: https://issues.apache.org/jira/browse/YARN-7586
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>            Priority: Blocker
>         Attachments: YARN-7586.1.patch, YARN-7586.2.patch, YARN-7586.3.patch, YARN-7586.4.patch
> YARN-7419 moved Application placement from RMAppManager to RMAppImpl which causes issues
since ApplicationSubmissionContext still has the original queue specified by the user and
not the mapped queue . This causes issues while doing ACL checks in RMAppManager

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