[jira] [Created] (YARN-10908) Investigate: Why AbstractCSQueue#authorizer is constructed for each queue

["Szilard Nemeth (Jira)" <ji...@apache.org>]

Szilard Nemeth created YARN-10908:
-------------------------------------

             Summary: Investigate: Why AbstractCSQueue#authorizer is constructed for each queue
                 Key: YARN-10908
                 URL: https://issues.apache.org/jira/browse/YARN-10908
             Project: Hadoop YARN
          Issue Type: Sub-task
            Reporter: Szilard Nemeth


AbstractCSQueue#hasAccess checks if a certain user with an ACL has permission to submit an app to the queue.
Checking the permission itself is performed by calling ConfiguredYarnAuthorizer#checkPermission. 
Interestingly, all queue objects have a reference to a YarnAuthorizationProvider instance.
What looks weird is how the authorizer is initialized: https://github.com/apache/hadoop/blob/ac0a4e7f589e7280268013c56339b3b257d332a0/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/AbstractCSQueue.java#L428
It just calls YarnAuthorizationProvider.getInstance with the Configuration object as an argument so actually, all queue objects have an instance constructed with the same configuration, and the getInstance method does not gather any queue-specific configuration value from the object so this is a waste of memory.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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