[ https://issues.apache.org/jira/browse/AMBARI-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Kropp updated AMBARI-15507: ----------------------------------- Fix Version/s: 2.4.0 > Support for Multiple Nameservices > --------------------------------- > > Key: AMBARI-15507 > URL: https://issues.apache.org/jira/browse/AMBARI-15507 > Project: Ambari > Issue Type: Bug > Affects Versions: trunk > Reporter: Henning Kropp > Fix For: 2.4.0 > > > 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: > # Restart fails, because HdfsResource does not work, related to > namenode_ha_utils.py > # (Blueprint) Install fails because DN's register with wrong cluster. How do > DN pick the right Nameservice? > # Alerting is broken because it configures namservices as being one > nameservice -- This message was sent by Atlassian JIRA (v6.3.4#6332)