[ https://issues.apache.org/jira/browse/HDFS-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079546#comment-17079546 ]
Hudson commented on HDFS-15269: ------------------------------- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18133 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/18133/]) HDFS-15269. NameNode should check the authorization API version only … (github: rev 061afcdf30ce10d04986672a0583d925d3f8f741) * (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSPermissionChecker.java * (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java * (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestAuthorizationContext.java > NameNode should check the authorization API version only once during > initialization > ----------------------------------------------------------------------------------- > > Key: HDFS-15269 > URL: https://issues.apache.org/jira/browse/HDFS-15269 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 3.3.0 > Reporter: Wei-Chiu Chuang > Assignee: Wei-Chiu Chuang > Priority: Blocker > > After HDFS-14743, every authorization check logs a messages like the following > {noformat} > 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 > {noformat} > 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. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org