[AMBARI-15777] Namenode startup does not detect HA when multiple nameservices defined

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: trunk
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Assignee: Dmytro Sen
• Reporter: Alex Bush
• Created: 08/Apr/16 13:26
• Updated: 21/Oct/16 10:00
• Resolved: 21/Oct/16 10:00

Description

When specifying multiple nameservices in dfs.nameservices, the correct nameservice and HA configuration is not detected resulting in a slow namenode startup and a message of:
'Must wait to leave safemode since High Availability is not enabled.'

This message is seen in:
https://github.com/apache/ambari/blob/6626796191833c77130302653d3afad5f4bf8aec/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py#L186

And is caused by:
https://github.com/apache/ambari/blob/291b7cbf5852db3fa37f4f180158d0958241e05b/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py#L243

dfs_ha_nameservices = default("/configurations/hdfs-site/dfs.nameservices", None)

This line should take into account dfs.internal.nameservices and perhaps choosing the first entry in dfs.nameservices if this field is comma separated and if dfs.internal.nameservices is not set.

The change should also be mirrored here:
https://github.com/apache/ambari/blob/291b7cbf5852db3fa37f4f180158d0958241e05b/ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_windows.py#L45

Issue Links

• Is contained by: AMBARI-15507 Support for Multiple Nameservices