[
https://issues.apache.org/jira/browse/HDFS-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Plush updated HDFS-1321:
----------------------------
Attachment: HDFS-1321-take4.txt
4 times the charm? :)
ok Hopefully addressed your last two issues, the assert fail was removed from
the test and the logline now reads as:
"dfs.namenode.rpc-address (localhost/127.0.0.1:9000) and
dfs.namenode.http-address (/127.0.0.1:9000) configuration keys are bound to the
same port, unable to start NameNode. Port: 9000"
> 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-take2.txt, HDFS-1321-take3.txt,
> HDFS-1321-take4.txt, 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
