[
https://issues.apache.org/jira/browse/HDFS-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091234#comment-14091234
]
Hudson commented on HDFS-6823:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #6038 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/6038/])
HDFS-6823. dfs.web.authentication.kerberos.principal shows up in logs for
insecure HDFS (raviprak:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1616846)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
HDFS-6823. dfs.web.authentication.kerberos.principal shows up in logs for
insecure HDFS (raviprak:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1616845)
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSUtil.java
> dfs.web.authentication.kerberos.principal shows up in logs for insecure HDFS
> ----------------------------------------------------------------------------
>
> Key: HDFS-6823
> URL: https://issues.apache.org/jira/browse/HDFS-6823
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Minor
> Fix For: 3.0.0, 2.6.0
>
> Attachments: HDFS-6823.patch
>
>
> Starting the namenode on a system not running Kerberos results in the
> following showing up in the log:
> {code}
> 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
> {code}
> If Kerberos isn't configured, we shouldn't try to display the principal
> message, never mind the raw text of the configuration option.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
