[AMBARI-12893] Adding host group in the blueprint for NameNode HA fails in installation

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: blueprints
• Assignee: Unassigned
• Reporter: Anandha L Ranganathan
• Created: 27/Aug/15 02:20
• Updated: 27/Aug/15 02:20

Description

The configuration looks like this in the hadoop-env.

The configuration looks like this for NameNode HA in the blueprint.

hadoop-ev{

"dfs_ha_initial_namenode_active": "%HOSTGROUP::host_group_master_1%"
"dfs_ha_initial_namenode_standby": "%HOSTGROUP::host_group_master_2"
}

hdfs-site

{ "dfs.client.failover.proxy.provider.dfs-nameservices": "org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider", "dfs.ha.automatic-failover.enabled": "true", "dfs.ha.fencing.methods": "shell(/bin/true)", "dfs.ha.namenodes.dfs-nameservices": "nn1,nn2", "dfs.namenode.http-address.dfs-nameservices.nn1": "%HOSTGROUP::host_group_master_1%:50070", "dfs.namenode.http-address.dfs-nameservices.nn2": "%HOSTGROUP::host_group_master_2%:50070", "dfs.namenode.https-address.dfs-nameservices.nn1": "%HOSTGROUP::host_group_master_1%:50470", "dfs.namenode.https-address.dfs-nameservices.nn2": "%HOSTGROUP::host_group_master_2%:50470", "dfs.namenode.rpc-address.dfs-nameservices.nn1": "%HOSTGROUP::host_group_master_1%:8020", "dfs.namenode.rpc-address.dfs-nameservices.nn2": "%HOSTGROUP::host_group_master_2%:8020", "dfs.namenode.shared.edits.dir": "qjournal://%HOSTGROUP::host_group_master_1%:8485;%HOSTGROUP::host_group_master_2%:8485;%HOSTGROUP::host_group_master_3%:8485/dfs-nameservices", "dfs.nameservices": "dfs-nameservices" }

core-site

{ "fs.defaultFS": "hdfs://dfs-nameservices", "ha.zookeeper.quorum": "%HOSTGROUP::host_group_master_1%:2181,%HOSTGROUP::host_group_master_2%:2181,%HOSTGROUP::host_group_master_3%:2181" }

During the installation it fails and one of the master_host sill the configuration is showing as host_group rather than FQDN.

The active namenode is substituted by FQDN but not the the standby node.

I am using Ambari 2.1 version.

hadoop-env{

"dfs_ha_initial_namenode_active": "usw2ha3dpma01.local",
"hadoop_root_logger": "INFO,RFA",
"dfs_ha_initial_namenode_standby": "%HOSTGROUP::host_group_master_2%",
"namenode_opt_permsize": "128m"
}