[
https://issues.apache.org/jira/browse/AMBARI-15506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241377#comment-15241377
]
Hudson commented on AMBARI-15506:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4655 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4655/])
AMBARI-15506 Support for multiple Namservices in namenode_ha_utils.py (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8f1279baeb5fb787a66dfda3f491b5bb88e315f])
*
ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
* ambari-agent/src/test/python/resource_management/TestNamenodeHaUtils.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
> Assignee: Henning Kropp
> Fix For: 2.4.0
>
> Attachments: AMBARI-15506, AMBARI-15506_1, AMBARI-15506_2,
> AMBARI-15506_3, AMBARI-15506_5, AMBARI-15506_regex,
> AMBARI-15506_regex_unit_tests-trunk_1.patch, namenode_ha_utils.py
>
>
> 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)
