[jira] [Commented] (AMBARI-15169) 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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166370#comment-15166370 ] 

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/12789637/AMBARI-15169.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5554//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.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:
> Set a custom hdfs-site property "ambari.namenode.hosts" that provides the mapping of namenodes to hosts.
> For example I set the custom property to
> {code}
> "ambari.namenode.hosts" : "{ 'nn1' : 'jay-homed-1' , 'nn2' : 'jay-homed-2' }"
> {code}
> For Non-HA, this should be set to the following
> {code}
> "ambari.namenode.hosts" : "{ 'nn' : 'jay-homed-1' }"
> {code}
> Ambari-Web should set ambari.namenode.hosts dynamically during
> - Fresh Cluster Install
> - Enable Namenode HA
> - Move Namenode
> Ambari Web changes will be handled separately. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)