[HDFS-4448] Allow HA NN to start in secure mode with wildcard address configured

• 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
• Target Version/s: 2.0.3-alpha
• Assignee: Aaron Myers
• Reporter: Aaron Myers
• Created: 29/Jan/13 04:07
• Updated: 30/Aug/16 01:42
• Resolved: 23/Apr/15 08:47

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.