Bug 1149055
| Summary: | [RFE][sahara]: Enable HDFS NameNode High Availability in HDP 2.* plugin | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
| Component: | openstack-sahara | Assignee: | Elise Gafford <egafford> |
| Status: | CLOSED ERRATA | QA Contact: | Luigi Toscano <ltoscano> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | unspecified | CC: | kbasil, markmc, matt, mimccune, mlopes, yeylon |
| Target Milestone: | Upstream M1 | Keywords: | FutureFeature |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/sahara/+spec/hdp-plugin-enable-hdfs-ha | ||
| Whiteboard: | upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented | ||
| 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 13:14:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
RHOS Integration
2014-10-03 04:01:10 UTC
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 |