Pausing a Cluster in AWS
Shutting Down and Starting Up the Cluster
- For AWS actions, use one of the following interfaces:
- AWS console
- AWS CLI
- AWS API
- For cluster actions, use one of the following interfaces:
- The Cloudera Manager web UI
- The Cloudera API start and stop commands
Shutdown procedure
- Navigate to the Cloudera Manager web UI.
- Stop the cluster.
- On the tab, click to the right of the cluster name and select Stop.
- Click Stop in the confirmation screen. The Command Details window
shows the progress of stopping services.
When All services successfully stopped appears, the task is complete and you can close the Command Details window.
- Stop the Cloudera Management Service.
- On the tab, click to the right of the service name and select Stop.
- Click Stop in the next screen to confirm. When you see a Finished status, the service has stopped.
- In AWS, stop all cluster EC2 instances, including the Cloudera Manager host .
Startup procedure
- In AWS, start all cluster EC2 instances.
- Navigate to the Cloudera Manager UI.
- Start the Cloudera Management Service.
- On the tab, click to the right of the service name and select Start.
- Click Start in the next screen to confirm. When you see a Finished status, the service has started.
- Start the cluster.
- On the tab, click to the right of the cluster name and select Start.
- Click Start that appears in the next screen to confirm. The Command
Details window shows the progress of starting services.
When All services successfully started appears, the task is complete and you can close the Command Details window.
More information
For more information about stopping the Cloudera Management Service, see Stopping the Cloudera Management Service in the Cloudera Enterprise documentation.
For more information about restarting the Cloudera Management Service, see Restarting the Cloudera Management Service in the Cloudera Enterprise documentation.
For more information about starting and stopping a cluster in Cloudera Manager, see Starting, Stopping, Refreshing, and Restarting a Cluster in the Cloudera Enterprise documentation.
For more information about stopping and starting EC2 instances, see Stop and Start Your Instance in the AWS documentation.
Considerations after Restart
- After starting the EC2 instances, Cloudera Manager and its agents will be running but the cluster will be stopped. There will be gaps in Cloudera Manager’s time-based metrics and charts.
- EC2 instances retain their internal IP address and hostname for their lifetime, so no reconfiguration of CDH is required after restart. The public IP and DNS hostnames, however, will be different. Elastic IPs can be configured to remain associated with a stopped instance at additional cost, but it isn’t necessary to maintain proper cluster operation.
<< Starting, Stopping, Refreshing, and Restarting a Cluster | ©2016 Cloudera, Inc. All rights reserved | Renaming a Cluster >> |
Terms and Conditions Privacy Policy |