[HDFS-2894] HA: automatically determine the nameservice Id if only one nameservice is configured

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HA branch (HDFS-1623)
• Component/s: ha
• Target Version/s: HA branch (HDFS-1623)
• Hadoop Flags: Reviewed
• Assignee: Eli Collins
• Reporter: Eli Collins
• Created: 04/Feb/12 23:46
• Updated: 22/Jun/12 05:02
• Resolved: 06/Feb/12 08:28

Description

The SecondaryNameNode should log a message and refuse to start if HA is enabled since the StandbyNode checkpoints by default and IIRC we have not yet enabled the ability to have multiple checkpointers in the NN.

On the HA branch the 2NN does not currently start from start-dfs.sh because getconf -secondarynamenodes claims the http-address is not configured even though it is, though this seems like a bug, in branch 23 getconf will correctly return localhost:50090.

 <property>
   <name>dfs.namenode.secondary.http-address</name>
   <value>localhost:50090</value>
 </property>

</configuration>
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs getconf -secondarynamenodes
Incorrect configuration: secondary namenode address dfs.namenode.secondary.http-address is not configured.

Issue Links

• is related to: HDFS-2893 The start/stop scripts don't start/stop the 2NN when using the default configuration