[HDFS-2893] The start/stop scripts don't start/stop the 2NN when using the default configuration

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.23.1
• Fix Version/s: 0.23.1
• Target Version/s: 0.23.1
• Hadoop Flags: Reviewed
• Assignee: Eli Collins
• Reporter: Eli Collins
• Created: 04/Feb/12 23:08
• Updated: 22/Jun/12 05:02
• Resolved: 06/Feb/12 09:02

Description

HDFS-1703 changed the behavior of the start/stop scripts so that the masters file is no longer used to indicate which hosts to start the 2NN on. The 2NN is now started, when using start-dfs.sh, on hosts only when dfs.namenode.secondary.http-address is configured with a non-wildcard IP. This means you can not start a NN using an http-address specified using a wildcard IP. We should allow a 2NN to be started with the default config, ie start-dfs.sh should start a NN, 2NN and DN. The packaging already works this way (it doesn't use start-dfs.sh, it uses hadoop-daemon.sh directly w/o first checking getconf) so let's bring start-dfs.sh in line with this behavior.

Issue Links

• relates to: HDFS-2894 HA: automatically determine the nameservice Id if only one nameservice is configured
• relates to: HDFS-1703 HDFS federation: Improve start/stop scripts and add script to decommission datanodes
• relates to: HDFS-2995 start-dfs.sh should only start the 2NN for namenodes with dfs.namenode.secondary.http-address configured