You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2020/04/08 00:47:00 UTC
[jira] [Created] (HDFS-15269) NameNode should check the
authorization API version only once during initialization
Wei-Chiu Chuang created HDFS-15269:
--------------------------------------
Summary: 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
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. This will result in serious performance regression.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org