[
https://issues.apache.org/jira/browse/AMBARI-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166703#comment-15166703
]
Hadoop QA commented on AMBARI-15169:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12789830/AMBARI-15169.2.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-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5558//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5558//console
This message is automatically generated.
> namenode_ha_utils.py returns sometimes Active NNs as emtpy set, and Stand-by
> NN as a set of 2 NNs in multi-homed environment
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-15169
> URL: https://issues.apache.org/jira/browse/AMBARI-15169
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.2.0
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Fix For: 2.2.2
>
> Attachments: AMBARI-15169.2.patch, AMBARI-15169.patch
>
>
> Steps to Reproduce:
> - Setup multi-homed cluster
> - Upgrade from Ambari 1.7 to Ambari-2.0.2
> - Upgrade from Ambari 2.0.2 to Ambari 2.2.0
> - Try starting Hive Server2 and it fails saying no Active NN
> This happens because we optimized to use webhdfs by default instead of hadoop
> jar calls.
> https://issues.apache.org/jira/browse/AMBARI-11347
> Fix:
> Use dfs.namenode.rpc-address property to get the host/ip. This key should be
> an actual ip/host:port
> See comments in https://issues.apache.org/jira/browse/HDFS-7586
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
