[ https://issues.apache.org/jira/browse/HDFS-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053969#comment-13053969 ]
Hadoop QA commented on HDFS-1321: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12483619/HDFS-1321.patch against trunk revision 1138645. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 4 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/828//console This message is automatically generated. > If service port and main port are the same, there is no clear log message > explaining the issue. > ----------------------------------------------------------------------------------------------- > > Key: HDFS-1321 > URL: https://issues.apache.org/jira/browse/HDFS-1321 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.23.0 > Reporter: gary murry > Assignee: Jim Plush > Priority: Minor > Labels: newbie > Fix For: 0.23.0 > > Attachments: HDFS-1321.patch > > > With the introduction of a service port to the namenode, there is now a > chance for user error to set the two port equal. This will cause the > namenode to fail to start up. It would be nice if there was a log message > explaining the port clash. Or just treat things as if the service port was > not specified. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira