[ https://issues.apache.org/jira/browse/HDFS-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310081#comment-14310081 ]
Hadoop QA commented on HDFS-7684: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12697096/HDFS.7684.001.patch against trunk revision eaab959. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 2 new or modified test files. {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:red}-1 release audit{color}. The applied patch generated 1 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.balancer.TestBalancer org.apache.hadoop.hdfs.TestLeaseRecovery2 Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/9464//testReport/ Release audit warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/9464//artifact/patchprocess/patchReleaseAuditProblems.txt Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9464//console This message is automatically generated. > 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.001.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)