Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1149055 - [RFE][sahara]: Enable HDFS NameNode High Availability in HDP 2.* plugin
[RFE][sahara]: Enable HDFS NameNode High Availability in HDP 2.* plugin
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-sahara (Show other bugs)
unspecified
Unspecified Unspecified
urgent Severity medium
: Upstream M1
: 7.0 (Kilo)
Assigned To: Elise Gafford
Luigi Toscano
https://blueprints.launchpad.net/saha...
upstream_milestone_kilo-1 upstream_de...
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-03 00:01 EDT by RHOS Integration
Modified: 2015-08-05 09:14 EDT (History)
6 users (show)

See Also:
Fixed In Version: openstack-sahara-2015.1.0-2.el7ost
Doc Type: Enhancement
Doc Text:
This enhancement adds namenode high availability as a supported option in the HDP 2.0.6 plugin. Users can signal that they require a cluster to be generated in HA mode, by passing a cluster with a quorum of zookeeper servers and journalnodes, and at least 2 namenodes. For example: "cluster_configs": { "HDFSHA": { "hdfs.nnha": true } }
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-05 09:14:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2015:1548 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2015-08-05 13:07:06 EDT

  None (edit)
Description RHOS Integration 2014-10-03 00:01:10 EDT
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
Comment 4 Luigi Toscano 2015-07-13 13:53:59 EDT
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
Comment 6 errata-xmlrpc 2015-08-05 09:14:11 EDT
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

Note You need to log in before you can comment on or make changes to this bug.