This section describes setting up Hadoop 2.x. It includes:
- I. Setting Up Ambari
- I.1. Getting Ready
- 1. Determine Version Compatibility
- 2. Understand the Basics
- 3. Meet Minimum System Requirements
- 4. Collect Information
- 5. Prepare the Environment
- 6. Optional: Configure Ambari for Local Repositories
- I.2. Running the Ambari Installer
- 1. Set Up the Bits
- 2. Set Up the Server
- 3. Optional: Set Up LDAP or Active Directory Authentication
- 4. Optional: Set Up Security for Ambari
- 5. Optional: Set Up Two-Way SSL Between Ambari Server and Ambari Agents
- 6. Optional: Change the Ambari Server Port
- 7. Optional: Configure Ambari Server for Internet Proxy
- 8. Start the Ambari Server
- I.1. Getting Ready
- II. Hadoop 2.x - Deploying, Configuring, and Upgrading Ambari
- II.3. Hadoop 2.x - Installing, Configuring, and Deploying the Cluster
- II.4. Hadoop 2.x - Troubleshooting Ambari Deployments
- 1. Review Ambari Log Files
- 2. Quick Checks
- 3. Specific Issues
- 3.1. Problem: Browser crashed before Install Wizard completed
- 3.2. Problem: Install Wizard reports that the cluster install has failed
- 3.3. Problem: “Unable to create new native thread” exceptions in HDFS DataNode logs or those of any system daemon
- 3.4. Problem: The “yum install ambari-server” Command Fails
- 3.5. Problem: HDFS Smoke Test Fails
- 3.6. Problem: The HCatalog Daemon Metastore Smoke Test Fails
- 3.7. Problem: MySQL and Nagios fail to install on RightScale CentOS 5 images on EC2
- 3.8. Problem: Trouble starting Ambari on system reboot
- 3.9. Problem: Metrics and Host information display incorrectly in Ambari Web
- 3.10. Problem: On SUSE 11 Ambari Agent crashes within the first 24 hours
- 3.11. Problem: Attempting to Start HBase REST server causes either REST server or Ambari Web to fail
- 3.12. Problem: Multiple Ambari Agent processes are running, causing re-register
- 3.13. Problem: Some graphs do not show a complete hour of data until the cluster has been running for an hour
- 3.14. Problem: After performing a cluster install the Nagios server is not started
- 3.15. Problem: A service with a customized service user is not appearing properly in Ambari Web
- 3.16. Problem: Updated configuration changes are not pushed to client/gateway nodes
- II.5. Appendix: Upgrading Ambari Server to 1.4.4
- II.6. Appendix: Upgrading the HDP Stack from 1.3.2 or later to 2.0.6
- II.7. Appendix: Hadoop 2.x - Configuring Ports
- II.8. Appendix: NameNode High Availabilty
- 1. Setting Up NameNode High Availabilty
- 1.1. Rolling Back NameNode HA
- 1.1.1. Stop HBase
- 1.1.2. Checkpoint the Active NameNode
- 1.1.3. Stop All Services
- 1.1.4. Prepare the Ambari Server Host for Rollback
- 1.1.5. Restore the HBase Configuration
- 1.1.6. Delete ZK Failover Controllers
- 1.1.7. Modify HDFS Configurations
- 1.1.8. Recreate the Secondary NameNode
- 1.1.9. Re-enable the Secondary NameNode
- 1.1.10. Delete All JournalNodes
- 1.1.11. Delete the Additional NameNode
- 1.1.12. Verify your HDFS Components
- 1.1.13. Start HDFS
- 1.1. Rolling Back NameNode HA
- 1. Setting Up NameNode High Availabilty
- III. Hadoop 1.x - Deploying, Configuring, and Upgrading Ambari
- III.9. Hadoop 1.x - Installing, Configuring, and Deploying the Cluster
- III.10. Troubleshooting Ambari Deployments
- 1. Review Ambari Log Files
- 2. Quick Checks
- 3. Specific Issues
- 3.1. Problem: Browser crashed before Install Wizard completed
- 3.2. Problem: Install Wizard reports that the cluster install has failed
- 3.3. Problem: “Unable to create new native thread” exceptions in HDFS DataNode logs or those of any system daemon
- 3.4. Problem: The “yum install ambari-server” Command Fails
- 3.5. Problem: HDFS Smoke Test Fails
- 3.6. Problem: The HCatalog Daemon Metastore Smoke Test Fails
- 3.7. Problem: MySQL and Nagios fail to install on RightScale CentOS 5 images on EC2
- 3.8. Problem: Trouble starting Ambari on system reboot
- 3.9. Problem: Metrics and Host information display incorrectly in Ambari Web
- 3.10. Problem: On SUSE 11 Ambari Agent crashes within the first 24 hours
- 3.11. Problem: Attempting to Start HBase REST server causes either REST server or Ambari Web to fail
- 3.12. Problem: Multiple Ambari Agent processes are running, causing re-register
- 3.13. Problem: Some graphs do not show a complete hour of data until the cluster has been running for an hour
- 3.14. Problem: After performing a cluster install the Nagios server is not started
- 3.15. Problem: A service with a customized service user is not appearing properly in Ambari Web
- 3.16. Problem: Updated configuration changes are not pushed to client/gateway nodes
- III.11. Appendix: Upgrading Ambari Server to 1.4.4
- III.12. Appendix: Upgrading Ambari Server to 1.2.5
- III.13. Appendix: Upgrading the HDP Stack to 1.3.3
- III.14. Appendix: Configuring Ports
- III.15. Configuring RHEL HA for Hadoop 1.x
- IV. Additional Tasks with Ambari
- IV.16. Appendix: Installing Ambari Agents Manually
- IV.17. Appendix: Using Custom Hostnames
- IV.18. Appendix: Upgrading Operating Systems on an Ambari-based Hadoop Installation
- IV.19. Appendix: Moving the Ambari Server
- IV.20. Appendix: Using Non-Default Databases
- IV.21. Setting Up Kerberos for Use with Ambari