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

Refactor name node to allow different token verification implementations

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.3.0, 3.1.4, 3.2.2
    • None
    • None

    Description

      Router currently uses Namenode web resources to read and verify delegation tokens. This model doesn't work when router will be deployed in secured mode. This change will introduce router's own UserProvider resource and dependencies.

      In the current deployment one can see this exception.

      {"RemoteException":{"exception":"ClassCastException","javaClassName":"java.lang.ClassCastException","message":"org.apache.hadoop.hdfs.server.federation.router.Router cannot be cast to org.apache.hadoop.hdfs.server.namenode.NameNode"}}

      In the proposed change, router will maintain its own web resource, that will be similar to current namenode, but modified to get back a router instance instead of namenode.

       

       

      Attachments

        1. HDFS-14006.003.patch
          7 kB
          CR Hota
        2. HDFS-14006.002.patch
          7 kB
          CR Hota
        3. HDFS-14006.001.patch
          6 kB
          CR Hota

        Issue Links

          Activity

            People

              crh CR Hota
              crh CR Hota
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: