9.2. Aborting a Rolling Restart
To abort future restart operations in the batch, choose Abort Rolling Restart.
- 1. Overview: Ambari User's Guide
- 2. Monitoring and Managing Your Cluster
- 3. Managing Hosts
- 1. Working with Hosts
- 2. Determining Host Status
- 3. Filtering the Hosts List
- 4. Performing Host-Level Actions
- 5. Viewing Components on a Host
- 6. Decommissioning Masters and Slaves
- 7. How to Delete a Component
- 8. Deleting a Host from a Cluster
- 9. Setting Maintenance Mode
- 10. Adding Hosts to a Cluster
- 11. Rack Awareness
- 4. Managing Services
- 1. Starting and Stopping All Services
- 2. Selecting a Service
- 3. Adding a Service
- 4. Editing Service Config Properties
- 5. Viewing Service Summary and Alerts
- 6. Performing Service Actions
- 7. Monitoring Background Operations
- 8. Using Quick Links
- 9. Rolling Restarts
- 10. Refreshing YARN Capacity Scheduler
- 11. Rebalancing HDFS
- 5. Managing Service High Availability
- 1. NameNode High Availability
- 1.1. How To Configure NameNode High Availability
- 1.2. How to Roll Back NameNode HA
- 1.2.1. Stop HBase
- 1.2.2. Checkpoint the Active NameNode
- 1.2.3. Stop All Services
- 1.2.4. Prepare the Ambari Server Host for Rollback
- 1.2.5. Restore the HBase Configuration
- 1.2.6. Delete ZooKeeper Failover Controllers
- 1.2.7. Modify HDFS Configurations
- 1.2.8. Recreate the Standby NameNode
- 1.2.9. Re-enable the Standby NameNode
- 1.2.10. Delete All JournalNodes
- 1.2.11. Delete the Additional NameNode
- 1.2.12. Verify the HDFS Components
- 1.2.13. Start HDFS
- 2. ResourceManager High Availability
- 3. HBase High Availability
- 4. Hive High Availability
- 5. Storm High Availability
- 6. Oozie High Availability
- 1. NameNode High Availability
- 6. Managing Configurations
- 7. Administering the Cluster
- 8. Monitoring and Alerts