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

NamenodeProtocol has the wrong value for clientPrincipal in KerberosInfo annotation

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.2-alpha
    • Fix Version/s: 2.0.3-alpha, 1.3.0
    • Component/s: namenode
    • Labels:
      None

      Description

      The @KerberosInfo annotation specifies the expected server and client principals for a given protocol in order to look up the correct principal name from the config. The NamenodeProtocol has the wrong value for the client config key. This wasn't noticed because most setups actually use the same value for for both the NN and 2NN principals (hdfs/_HOST@REALM), in which the _HOST part gets replaced at run-time. This bug therefore only manifests itself on secure setups which explicitly specify the NN and 2NN principals.

        Attachments

        1. HDFS-2264.b1.patch
          6 kB
          Jing Zhao
        2. HDFS-2264.patch
          5 kB
          Aaron T. Myers
        3. HDFS-2264.patch
          5 kB
          Aaron T. Myers
        4. HDFS-2264.r1.diff
          0.8 kB
          Harsh J

          Issue Links

            Activity

              People

              • Assignee:
                atm Aaron T. Myers
                Reporter:
                atm Aaron T. Myers
              • Votes:
                0 Vote for this issue
                Watchers:
                17 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: