[jira] [Updated] (AMBARI-15506) Support for multiple Namservices in namenode_ha_utils.py

["Henning Kropp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-15506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Henning Kropp updated AMBARI-15506:
-----------------------------------
    Attachment: AMBARI-15506

Introduces {{get_nameservice(hdfs_site)}} in namenode_ha_utils.py

> Support for multiple Namservices in namenode_ha_utils.py
> --------------------------------------------------------
>
>                 Key: AMBARI-15506
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15506
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: trunk
>         Environment: HDFS HA
>            Reporter: Henning Kropp
>         Attachments: AMBARI-15506
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)