Uninstalling Cloudera Manager
If necessary, you can use the following instructions to uninstall the Cloudera Manager Server and Agents.

If you have come to this page because your installation did not complete (for example, if it was interrupted by a virtual machine timeout), and you want to proceed with the installation, do the following:
- Remove files and directories:
$ sudo rm -Rf /usr/share/cmf /var/lib/cloudera* /var/cache/yum/cloudera*
- Run the installer again.
Uninstalling Cloudera Manager Server and Agents

After uninstalling Cloudera Manager, you may want to keep or remove the Hadoop data on your cluster. The following instructions do not remove the Hadoop data. To find out where the Hadoop data directories are located, you can navigate to the Configuration tab for the HDFS and MapReduce services in the Cloudera Manager Admin Console, and search for the Data Directory property setting. For additional information about uninstalling CDH, including clean-up of CDH files, see the entry on Uninstalling CDH Components in the Maintenance Tasks and Notes topic in the CDH4 Installation Guide.
Step 1: Stop all services
You must stop all Hadoop services before uninstalling the Cloudera Manager Server and Agents.

As necessary, repeat the process of stopping services for each cluster.
To stop all services
- In the Cloudera Manager Admin Console, select Services > All Services.
- Click the top Actions button that corresponds to the cluster and choose 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 may close the Command Details window.
- For each Cloudera Management Service entry, click Actions and click 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 may close the Command Details window.
Step 2: Deactivate and remove Parcels, if used for CDH installation.
If you installed CDH using parcels, you should remove them from the Parcels page in the Cloudera Manager Admin Console.
If you installed using packages, you can skip this step. Go to Step 3. |
- Click the parcel indicator in the top navigation bar. This takes you to the Administration page, Parcels tab. By default, any parcels available for download or distribution are shown, as well as the activated parcel.
- Click the arrow on the Actions button and select Deactivate.
When this action has completed, the parcel button will change to say Activate.
- Click the arrow on the Activate button and select Remove from Hosts.
When this action has completed, the parcel button will change to say Distribute.
- Click the arrow on the Distribute button and select Delete. This will remove the parcel from the local parcel repository.
Note that there can only be one active parcel; however, there may be multiple parcels that have been downloaded and distributed, but that are not active. If this is the case, you should also remove those parcels from any hosts onto which they have been distributed, and delete the parcels from the local repository.
Step 3: Uninstall the Cloudera Manager Server.
The commands for uninstalling the Cloudera Manager Server depend on the method you used to install the Cloudera Manager Server. Refer to section below that corresponds to the method you used to install the Cloudera Manager Server. This process described below also removes the embedded PostgreSQL database, if you installed that option. If you did not use the PostgreSQL database, omit the cloudera-manager-server-db steps.
If you used the cloudera-manager-installer.bin file:
If you installed the Cloudera Manager Server using cloudera-manager-installer.bin, run the following command on the Cloudera Manager Server host:
$ sudo /usr/share/cmf/uninstall-cloudera-manager.sh

If the uninstall-cloudera-manager.sh is not installed on your cluster, use the following instructions to uninstall the Cloudera Manager Server.
If you did not use the cloudera-manager-installer.bin file:
If you installed the Cloudera Manager Server using a different installation method such as Puppet, run the following commands on the Cloudera Manager Server host.
- Stop the Cloudera Manager Server and its database:
sudo service cloudera-scm-server stop sudo service cloudera-scm-server-db stop
- Uninstall the Cloudera Manager Server and its database:
On Red Hat systems:
sudo yum remove cloudera-manager-server sudo yum remove cloudera-manager-server-db
On SLES systems:
sudo zypper -n rm --force-resolution cloudera-manager-server sudo zypper -n rm --force-resolution cloudera-manager-server-db
On Debian/Ubuntu systems:
sudo apt-get remove cloudera-manager-server sudo apt-get remove cloudera-manager-server-db
Step 4: On all Agent hosts, uninstall CDH and the Cloudera Manager Agents.
If you installed using packages:
On all Agent hosts, run the following commands as root to uninstall the Cloudera Manager Agent and CDH on your cluster machines.
- Stop the Cloudera Manager agent.
On Red Hat/SLES systems:
$ sudo service cloudera-scm-agent hard_stop
On Debian/Ubuntu systems:
$ sudo /usr/sbin/service cloudera-scm-agent hard_stop
- Uninstall the CDH and Cloudera Manager packages:
On Red Hat systems: If you are running CDH3:
$ sudo yum remove 'cloudera-manager-*' hadoop-0.20 hue-common hadoop-pig oozie-client hive hadoop-hbase hadoop-zookeeper bigtop-utils
If you are running CDH4 (including Impala):
$ sudo yum remove 'cloudera-manager-*' hadoop hue-common 'bigtop-*'
On Red SLES systems: If you are running CDH3:
$ sudo zypper remove 'cloudera-manager-*' hadoop-0.20 hue-common hadoop-pig oozie-client hive hadoop-hbase hadoop-zookeeper bigtop-utils
If you are running CDH4:
$ sudo zypper remove 'cloudera-manager-*' hadoop hue-common 'bigtop-*'
On Debian/Ubuntu systems: If you are running CDH3:
$ sudo apt-get purge 'cloudera-manager-*' hadoop-0.20 hue-common hadoop-pig oozie-client hive hadoop-hbase hadoop-zookeeper bigtop-utils
If you are running CDH4:
$ sudo apt-get purge 'cloudera-manager-*' hadoop hue-common 'bigtop-*'
- Run this command:
On Red Hat systems:
$ sudo yum clean all
On SLES systems:
$ sudo zypper clean
On Debian/Ubuntu systems:
$ sudo apt-get clean
If you installed using parcels:
On all Agent hosts, run the following commands as root to uninstall the Cloudera Manager Agent on your cluster machines. You should already have removed CDH by deactivating and deleting the parcel.
- Stop the Cloudera Manager agent.
On Red Hat/SLES systems:
$ sudo service cloudera-scm-agent hard_stop
On Debian/Ubuntu systems:
$ sudo /usr/sbin/service cloudera-scm-agent hard_stop
- Uninstall the Cloudera Manager packages:
On Red Hat systems:
$ sudo yum remove 'cloudera-manager-*'
On SLES systems:
$ sudo zypper remove 'cloudera-manager-*'
On Debian/Ubuntu systems:
$ sudo apt-get purge 'cloudera-manager-*'
- Run this command:
On Red Hat systems:
$ sudo yum clean all
On SLES systems:
$ sudo zypper clean
On Debian/Ubuntu systems:
$ sudo apt-get clean
Step 5: On all Agent hosts, remove all Cloudera Manager data.
This step permanently removes Cloudera Manager data. If you want to be able to access any of this data in the future, you must back it up before removing it. If you used an embedded PostgreSQL database, that data is stored in /var/lib/cloudera-scm-server-db. To permanently remove all Cloudera Manager data, run the following command as root:
$ sudo rm -Rf /usr/share/cmf /var/lib/cloudera* /var/cache/yum/cloudera*
Step 6: On all Agent hosts, kill any running Cloudera Manager and Hadoop processes.
On all Agent hosts, kill any running Cloudera Manager and Hadoop processes:
$ for u in hdfs mapred cloudera-scm hbase hue zookeeper oozie hive impala flume; do sudo kill $(ps -u $u -o pid=); done

This step should not be necessary if you stopped all the services and the Cloudera Manager agent correctly.
Step 7: Remove the Cloudera Manager lock file.
On all Agent hosts, run this command to remove the Cloudera Manager lock file:
$ sudo rm /tmp/.scm_prepare_node.lock
<< Previous: Deploying Clients | Next: Troubleshooting Installation and Upgrade Problems >> |