[
https://issues.apache.org/jira/browse/HDFS-15269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079611#comment-17079611
]
Brahma Reddy Battula commented on HDFS-15269:
---------------------------------------------
[~weichiu] thanks reporting and fixing this.. Added fixversion 3.4.0, as this
merged to 3.4.0 also.
> 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
> Fix For: 3.3.0, 3.4.0
>
>
> 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
