[
https://issues.apache.org/jira/browse/HDFS-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HDFS-2595:
-----------------------------------
Component/s: scripts
> misleading message when fs.default.name not set and running sbin/start-dfs.sh
> -----------------------------------------------------------------------------
>
> Key: HDFS-2595
> URL: https://issues.apache.org/jira/browse/HDFS-2595
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode, scripts
> Affects Versions: 0.23.0
> Reporter: Joe Crobak
> Priority: Minor
>
> sbin/start-dfs.sh calls {{bin/hdfs getconf -namenodes}} which reports the
> following error if the default value of fs.default.name from core-default.xml
> is used: {noformat}Incorrect configuration: namenode address
> dfs.namenode.servicerpc-address or dfs.namenode.rpc-address is not
> configured.{noformat}
> In previous versions of hadoop, I would see a slightly more helpful message:
> {noformat}org.apache.hadoop.hdfs.server.namenode.NameNode:
> java.lang.IllegalArgumentException: Does not contain a valid host:port
> authority: file:///{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
