Szilard Nemeth created YARN-10798: ------------------------------------- Summary: Enhancements in RMAppManager: createAndPopulateNewRMApp and copyPlacementQueueToSubmissionContext Key: YARN-10798 URL: https://issues.apache.org/jira/browse/YARN-10798 Project: Hadoop YARN Issue Type: Improvement Reporter: Szilard Nemeth Assignee: Szilard Nemeth
As a follow-up of YARN-10787, we need to do the following: 1. Rename RMAppManager#copyPlacementQueueToSubmissionContext: This method not really copies anything, it simply overrides the queue value. 2. Add Debug log to print csqueue object before the authorization code: [Code block|https://github.com/apache/hadoop/blob/2541efa496ba0e7e096ee5ec3c08d64b62036402/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/RMAppManager.java#L459-L475] 3. Fix log messages: As 'copyPlacementQueueToSubmissionContext' overrides (not copies) the original queue name with the queue name from the PlacementContext, all calls to submissionContext.getQueue() will return the short queue name. This results in very misleading log messages as well, including the exception message itself: {code} org.apache.hadoop.yarn.exceptions.YarnException: org.apache.hadoop.security.AccessControlException: User someuser1 does not have permission to submit application_1621540945412_0001 to queue somequeue {code} All log messages should print the original submission queue, if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org