[
https://issues.apache.org/jira/browse/HDFS-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14087194#comment-14087194
]
Hadoop QA commented on HDFS-6823:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12659998/HDFS-6823.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7565//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7565//console
This message is automatically generated.
> 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
> Reporter: Allen Wittenauer
> Priority: Minor
> 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)
