Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-4448

HA NN does not start with wildcard address configured for other NN when security is enabled

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0.3-alpha
    • Fix Version/s: None
    • 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.

      1. HDFS-4448.patch
        2 kB
        Aaron T. Myers
      2. HDFS-4448.patch
        2 kB
        Aaron T. Myers

        Activity

        No work has yet been logged on this issue.

          People

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

            Dates

            • Created:
              Updated:

              Development