Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-15269

NameNode should check the authorization API version only once during initialization

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Target Version/s:

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                weichiu Wei-Chiu Chuang
                Reporter:
                weichiu Wei-Chiu Chuang
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: