[
https://issues.apache.org/jira/browse/AMBARI-15169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-15169:
-----------------------------------
Description:
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.
was:
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}
> 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
>
>
> 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)
