[
https://issues.apache.org/jira/browse/HDFS-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200587#comment-13200587
]
Eli Collins commented on HDFS-2893:
-----------------------------------
Actually, I don't see why sbin/start-dfs.sh checks the return value of getconf
before starting the 2NN, seems like it should start the 2NN unconditionally.
The 2NN itself does not use DFSUtil#getSecondaryNameNodeAddresses and so will
start w/o a value for http-address being specified.
> The 2NN won't start if dfs.namenode.secondary.http-address is default or
> specified with a wildcard IP and port
> --------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-2893
> URL: https://issues.apache.org/jira/browse/HDFS-2893
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.1
> Reporter: Eli Collins
> Priority: Critical
>
> Looks like DFSUtil address matching doesn't find a match if the http-address
> is specified using a wildcard IP and a port. It should return 0.0.0.0:50090
> in this case which would allow the 2NN to start.
> Also, unless http-address is explicitly configured in hdfs-site.xml the 2NN
> will not start, since DFSUtil#getSecondaryNameNodeAddresses does not use the
> default value as a fallback. That may be confusing to people who expect the
> default value to be used.
> {noformat}
> hadoop-0.23.1-SNAPSHOT $ cat /home/eli/hadoop/conf3/hdfs-site.xml
> ...
> <property>
> <name>dfs.namenode.secondary.http-address</name>
> <value>0.0.0.0:50090</value>
> </property>
> </configuration>
> hadoop-0.23.1-SNAPSHOT $ ./bin/hdfs --config ~/hadoop/conf3 getconf
> -secondarynamenodes
> 0.0.0.0
> hadoop-0.23.1-SNAPSHOT $ ./sbin/start-dfs.sh
> Starting namenodes on [localhost]
> localhost: starting namenode, logging to
> /home/eli/hadoop/dirs3/logs/eli/hadoop-eli-namenode-eli-thinkpad.out
> localhost: starting datanode, logging to
> /home/eli/hadoop/dirs3/logs/eli/hadoop-eli-datanode-eli-thinkpad.out
> Secondary namenodes are not configured. Cannot start secondary namenodes.
> {noformat}
> This works if eg localhost:50090 is used.
> We should also update the hdfs user guide to remove the reference to the
> masters file since it's no longer used to configure which hosts the 2NN runs
> on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
