[
https://issues.apache.org/jira/browse/AMBARI-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168355#comment-15168355
]
Hudson commented on AMBARI-15169:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4391 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4391/])
AMBARI-15169: namenode_ha_utils.py returns sometimes Active NNs as emtpy
(jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4221872a6d9827ba3e026c767c3f3f7efe01bee0])
*
ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_ha_namenode_health.py
> 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)
