[
https://issues.apache.org/jira/browse/AMBARI-15506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235266#comment-15235266
]
Hadoop QA commented on AMBARI-15506:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12798012/AMBARI-15506_5
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6346//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6346//console
This message is automatically generated.
> 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, 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)
