Cloned from launchpad blueprint https://blueprints.launchpad.net/sahara/+spec/hdp-plugin-enable-hdfs-ha. Description: Configure and enable HDFS NameNode High Availability on Hadoop clusters deployed with HDP 2.* plugin. Specification URL (additional information): None
Following the upstream guidelines, an HDP 2.0.6 cluster setup according the following structure: * master-ha-common (1 node) - AMBARI_SERVER - HISTORYSERVER - OOZIE_SERVER - RESOURCEMANAGER - SECONDARY_NAMENODE - ZOOKEEPER_SERVER - JOURNALNODE * master-ha-nn (2 nodes) - NAMENODE - ZOOKEEPER_SERVER - JOURNALNODE * worker-ha (3 nodes) - DATANODE - HDFS_CLIENT - MAPREDUCE2_CLIENT - NODEMANAGER - OOZIE_CLIENT - PIG - YARN_CLIENT - ZOOKEEPER_CLIENT and using the following configuration key: "cluster_configs": { "HDFSHA": { "hdfs.nnha": true } } ends up with NameNode services configured in active/passive HA (two instances, one enabled, the other in failover mode). Jobs can be executed as Oozie points to the correct element. Tested on: openstack-sahara-api-2015.1.0-5.el7ost.noarch openstack-sahara-engine-2015.1.0-5.el7ost.noarch openstack-sahara-common-2015.1.0-5.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548