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

Allow HA NN to start in secure mode with wildcard address configured

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.3-alpha
    • Fix Version/s: 2.8.0, 3.0.0-alpha1
    • Component/s: ha, namenode, security
    • Labels:
      None

      Description

      Currently if one tries to configure HA NNs use the wildcard HTTP address when security is enabled, the NN will fail to start with an error like the following:

      java.lang.IllegalArgumentException: java.io.IOException: Cannot use a wildcard address with security. Must explicitly set bind address for Kerberos
      

      This is the case even if one configures an actual address for the other NN's HTTP address. There's no good reason for this, since we now check for the local address being set to 0.0.0.0 and determine the canonical hostname for Kerberos purposes using InetAddress.getLocalHost().getCanonicalHostName(), so we should remove the restriction.

        Attachments

        1. HDFS-4448.patch
          2 kB
          Aaron T. Myers
        2. HDFS-4448.patch
          2 kB
          Aaron T. Myers
        3. HDFS-4448.2.patch
          1 kB
          Arun Suresh

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: