[HDFS-15269] NameNode should check the authorization API version only once during initialization

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.3.0, 3.4.0
• Component/s: namenode
• Target Version/s: 3.3.0
• Assignee: Wei-Chiu Chuang
• Reporter: Wei-Chiu Chuang
• Created: 08/Apr/20 00:46
• Updated: 09/Apr/20 17:46
• Resolved: 09/Apr/20 16:46

Description

After HDFS-14743, every authorization check logs a messages like the following

2020-04-07 23:44:55,276 INFO org.apache.hadoop.security.UserGroupInformation: Default authorization provider supports the new authorization provider API
2020-04-07 23:44:55,276 INFO org.apache.hadoop.security.UserGroupInformation: Default authorization provider supports the new authorization provider API
2020-04-07 23:44:55,277 INFO org.apache.hadoop.security.UserGroupInformation: Default authorization provider supports the new authorization provider API
2020-04-07 23:44:55,278 INFO org.apache.hadoop.security.UserGroupInformation: Default authorization provider supports the new authorization provider API

The intend was to check for authorization provider's API compatibility during initialization but apparently it's not. This will result in serious performance regression.

Issue Links

• is broken by: HDFS-14743 Enhance INodeAttributeProvider/ AccessControlEnforcer Interface in HDFS to support Authorization of mkdir, rm, rmdir, copy, move etc...
• links to: GitHub Pull Request #1945