Alex Bush created AMBARI-15777:
----------------------------------
Summary: Namenode startup does detect HA when multiple
nameservices defined
Key: AMBARI-15777
URL: https://issues.apache.org/jira/browse/AMBARI-15777
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Alex Bush
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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
