Return-Path: 
 <hdfs-issues-return-109372-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 66EE810FB0
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Thu, 12 Feb 2015 21:45:20 +0000 (UTC)
Received: (qmail 92323 invoked by uid 500); 12 Feb 2015 21:45:14 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 92271 invoked by uid 500); 12 Feb 2015 21:45:14 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 92259 invoked by uid 99); 12 Feb 2015 21:45:14 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2015 21:45:14 +0000
Date: Thu, 12 Feb 2015 21:45:13 +0000 (UTC)
From: "Anu Engineer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12770310.1422353126000.31827.1423777513892@Atlassian.JIRA>
In-Reply-To: <JIRA.12770310.1422353126000@Atlassian.JIRA>
References: <JIRA.12770310.1422353126000@Atlassian.JIRA>
 <JIRA.12770310.1422353126880@arcas>
Subject: [jira] [Commented] (HDFS-7684) The host:port settings of
 dfs.namenode.secondary.http-address should be trimmed before use
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-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319042#comment-14319042 ] 

Anu Engineer commented on HDFS-7684:
------------------------------------

Addressed comments from  [~cnauroth] and [~ajisakaa]

> The host:port settings of dfs.namenode.secondary.http-address should be trimmed before use
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7684
>                 URL: https://issues.apache.org/jira/browse/HDFS-7684
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.4.1, 2.5.1
>            Reporter: Tianyin Xu
>            Assignee: Anu Engineer
>         Attachments: HDFS-7684.003.patch, HDFS-7684.004.patch, HDFS.7684.001.patch, HDFS.7684.002.patch
>
>
> With the following setting,
> <property>
> <name>dfs.namenode.secondary.http-address</name>
> <value>myhostname:50090 </value>
> </property>
> The secondary NameNode could not be started
> $ hadoop-daemon.sh start secondarynamenode
> starting secondarynamenode, logging to /home/hadoop/hadoop-2.4.1/logs/hadoop-hadoop-secondarynamenode-xxx.out
> /home/hadoop/hadoop-2.4.1/bin/hdfs
> Exception in thread "main" java.lang.IllegalArgumentException: Does not contain a valid host:port authority: myhostname:50090
> 	at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:196)
> 	at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:163)
> 	at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:152)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.getHttpAddress(SecondaryNameNode.java:203)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:214)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:192)
> 	at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:651)
> We were really confused and misled by the log message: we thought about the DNS problems (changed to IP address but no success) and the network problem (tried to test the connections with no success...)
> It turned out to be that the setting is not trimmed and the additional space character in the end of the setting caused the problem... OMG!!!...
> Searching on the Internet, we find we are really not alone.  So many users encountered similar trim problems! The following lists a few:
> http://solaimurugan.blogspot.com/2013/10/hadoop-multi-node-cluster-configuration.html
> http://stackoverflow.com/questions/11263664/error-while-starting-the-hadoop-using-strat-all-sh
> https://issues.apache.org/jira/browse/HDFS-2799
> https://issues.apache.org/jira/browse/HBASE-6973



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)