Pausing Cloudera Director Instances
The Cloudera Director server can be stopped at any time to reduce costs, as can clusters running on Microsoft Azure. These actions are described in the sections below.
Pausing the Cloudera Director Server
Although you can stop and start the Cloudera Director server at any time, you should wait for running workflows to complete.
To start or stop the server, enter the following command:
$ sudo service cloudera-director-server [start | stop]
Pausing a Cluster in Azure
There are times when it makes sense to shut down a cluster and stop your Azure virtual machines. The cluster will not be immediately available while stopped and it cannot be used to ingest or process data, but you won't be billed by Microsoft for virtual machines that are stopped and deallocated. Provisioned premium storage disks, and space used by standard storage disks will continue to accrue charges.
- Stop the cluster
- Stop Cloudera Management Service
- Stop all cluster virtual machines, including the Cloudera Manager host
- Start all cluster virtual machines
- Start Cloudera Management Service
- Start the cluster
After starting the virtual machines, 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.
Azure virtual machines that are configured with static private IP addresses will retain their internal IP address and hostname as long as the associated network interface object is not removed, so no reconfiguration of CDH is required after restart. If your nodes were provisioned via Cloudera Director, you should confirm that the IP configuration of your hosts is set to static before shutting down your cluster. The default for the Azure plugin in Cloudera Director 2.4.0 and earlier is dynamic. If you need to change the IP configuration from dynamic to static it can be done via the Azure Portal or PowerShell.
Dynamic public IP addresses will be different after virtual machine shutdown. Static public IP addresses can be configured to remain associated with a stopped virtual machine at additional cost, but it isn’t necessary to maintain proper cluster operation.