[
https://issues.apache.org/jira/browse/AMBARI-19206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764431#comment-15764431
]
Hadoop QA commented on AMBARI-19206:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844023/AMBARI-19206.patch
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
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9744//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9744//console
This message is automatically generated.
> When Namenode HA is enabled, hbase.rootdir property for ambari-metrics
> (distributed) does not get updated
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-19206
> URL: https://issues.apache.org/jira/browse/AMBARI-19206
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.0, 2.4.2
> Reporter: Sangeeta Ravindran
> Assignee: Sangeeta Ravindran
> Fix For: 2.5.0
>
> Attachments: AMBARI-19206.patch, AMSHbaseRootdirPostNNHAEnabling.jpg,
> NNHAWizard1.jpg, NNHAWizard2.jpg
>
>
> On a cluster with ambari-metrics in distributed operation mode, enable
> Namenode HA.
> After HA wizard is run, the amabri-metrics property for hbase.rootdir should
> point to hdfs://<Nameservice ID>, but it actually still points to the
> explicit Namenode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
