Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
trunk
-
None
-
HDFS HA
Description
Currently Ambari does not support the definition of multiple Nameservices. It is always assumed hdfs_site['dfs.nameservices'] is just a string defining one nameservice.
Multiple nameservices can be configured for exmaple to support seamless distcp between two HA clusters. The nameservices are defined as a comma separated list in hdfs_site['dfs.nameservices'].
This patch introduces the method get_nameservice(hdfs_site), which splits the value into in an array and identifies the nameservice for the current cluster with what is set in hdfs_site['dfs.namenode.shared.edits.dir']. By default the first nameservice is returned or empty.
To verify the current namservice it would be preferred to use fs.defaultFS in core-site, but getting this config into namenode_ha_utils.py seems more involved.
Attachments
Attachments
Issue Links
- Is contained by
-
AMBARI-15507 Support for Multiple Nameservices
- Resolved
- is related to
-
AMBARI-13946 Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail
- Resolved
- links to