Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D71D910AE1 for ; Fri, 8 Aug 2014 18:19:14 +0000 (UTC) Received: (qmail 85342 invoked by uid 500); 8 Aug 2014 18:19:14 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 85293 invoked by uid 500); 8 Aug 2014 18:19:14 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 85281 invoked by uid 99); 8 Aug 2014 18:19:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Aug 2014 18:19:14 +0000 Date: Fri, 8 Aug 2014 18:19:14 +0000 (UTC) From: "Ravi Prakash (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-6823) dfs.web.authentication.kerberos.principal shows up in logs for insecure HDFS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091083#comment-14091083 ] Ravi Prakash commented on HDFS-6823: ------------------------------------ Patch looks good to me. +1. The unit test failure is unrelated. It fails on an unpatched build as well. HDFS-4663 is open (although for an OOM, I don't think it makes sense to create another JIRA.) Will commit shortly. Thanks Allen! > 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)