[HDFS-6823] dfs.web.authentication.kerberos.principal shows up in logs for insecure HDFS

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.6.0
• Component/s: namenode
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Allen Wittenauer
• Reporter: Allen Wittenauer
• Created: 05/Aug/14 22:44
• Updated: 12/May/16 18:18
• Resolved: 08/Aug/14 18:29

Description

Starting the namenode on a system not running Kerberos results in the following showing up in the log:

2014-08-05 15:02:33,747 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: Clients are to use aw-mbp-work.local:9000 to access this namenode/service.
2014-08-05 15:02:33,831 WARN org.apache.hadoop.util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2014-08-05 15:02:33,948 INFO org.apache.hadoop.hdfs.DFSUtil: Starting web server as: ${dfs.web.authentication.kerberos.principal}
2014-08-05 15:02:33,948 INFO org.apache.hadoop.hdfs.DFSUtil: Starting Web-server for hdfs at: http://aw-mbp-work.local:50070

If Kerberos isn't configured, we shouldn't try to display the principal message, never mind the raw text of the configuration option.