[AMBARI-15507] Support for Multiple Nameservices

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Assignee: Henning Kropp
• Reporter: Henning Kropp
• Created: 22/Mar/16 09:45
• Updated: 26/Apr/16 07:36
• Resolved: 22/Apr/16 11:37

Description

This is an umbrella JIRA to collect issues related to the support of multiple Nameservices.

Currently all implementations in Amabari assume that hdfs_site['dfs.nameservices'] is just a string defining one nameservice, while it actually defines multiple nameservices.

Multiple nameservices can be configured for exmaple to support seamless distcp between two HA clusters.

At least 3 issues can be experienced:

1. Restart fails, because HdfsResource does not work, related to namenode_ha_utils.py
2. (Blueprint) Install fails because DN's register with wrong cluster. How do DN pick the right Nameservice?
3. Alerting is broken because it configures namservices as being one nameservice

Issue Links

• contains: AMBARI-15506 Support for multiple Namservices in namenode_ha_utils.py
• contains: AMBARI-15508 Enable HDFS alerts with multiple namservices
• contains: AMBARI-15509 Install with Multiple Nameservices can result in DN register with wrong cluster
• contains: AMBARI-15615 Populate property dfs.internal.nameservices when enabling NN HA
• contains: AMBARI-15777 Namenode startup does not detect HA when multiple nameservices defined
• relates to: AMBARI-15788 Ambari upgrade should auto-populate dfs.internal.nameservice
• relates to: AMBARI-15790 Clean up stack scripts that refer to dfs.nameservices to use dfs.internal.nameservices as first option
• relates to: AMBARI-15791 Blueprint based installations should automatically add dfs.internal.nameservices during cluster creation