NameNode High Availability
To ensure that another NameNode in your cluster is always available if the primary NameNode host fails, you should enable and configure NameNode high availability on your cluster using Ambari Web.
More Information
- 1. Ambari Operations: Overview
- 2. Understanding the Cluster Dashboard
- 3. Managing Hosts
- 4. Managing Services
- 5. Managing Service High Availability
- NameNode High Availability
- Configuring NameNode High Availability
- Rolling Back NameNode HA
- Stop HBase
- Checkpoint the Active NameNode
- Stop All Services
- Prepare the Ambari Server Host for Rollback
- Restore the HBase Configuration
- Delete ZooKeeper Failover Controllers
- Modify HDFS Configurations
- Re-create the Secondary NameNode
- Re-enable the Secondary NameNode
- Delete All JournalNodes
- Delete the Additional NameNode
- Verify the HDFS Components
- Start HDFS
- Managing Journal Nodes
- ResourceManager High Availability
- HBase High Availability
- Hive High Availability
- Storm High Availability
- Oozie High Availability
- Apache Atlas High Availability
- Enabling Ranger Admin High Availability
- NameNode High Availability
- 6. Managing Configurations
- 7. Administering the Cluster
- 8. Managing Alerts and Notifications
- 9. Using Ambari Core Services
- Understanding Ambari Metrics
- AMS Architecture
- Using Grafana
- Grafana Dashboards Reference
- AMS Performance Tuning
- AMS High Availability
- AMS Security
- Ambari Log Search (Technical Preview)
- Ambari Infra
- Understanding Ambari Metrics