Uninstalling Cloudera Manager and Managed Software

Use the following instructions to uninstall the Cloudera Manager Server, Agents, managed software, and databases.

Uninstalling Cloudera Manager and Managed Software

Record User Data Paths

The user data paths listed Remove User Data, /var/lib/flume-ng /var/lib/hadoop* /var/lib/hue /var/lib/navigator /var/lib/oozie /var/lib/solr /var/lib/sqoop* /var/lib/zookeeper data_drive_path/dfs data_drive_path/mapred data_drive_path/yarn, are the default settings. However, at some point they might have been reconfigured in Cloudera Manager. If you want to remove all user data from the cluster and have changed the paths, either when you installed CDH and managed services or at some later time, note the location of the paths by checking the configuration in each service.

Stop all Services

For each cluster managed by Cloudera Manager:

  1. For each cluster managed by Cloudera Manager:
    1. On the Home > Status tab, click to the right of the cluster name and select Stop.
    2. 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.
  2. On the Home > Status tab, click to the right of the Cloudera Management Service entry and select Stop. 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.

Deactivate and Remove Parcels

If you installed using packages, skip this step and go to Uninstall the Cloudera Manager Server; you will remove packages in Uninstall Cloudera Manager Agent and Managed Software. If you installed using parcels remove them as follows:
  1. Click the parcel indicator in the main navigation bar.
  2. In the Location selector on the left, select All Clusters.
  3. For each activated parcel, select Actions > Deactivate. When this action has completed, the parcel button changes to Activate.
  4. For each activated parcel, select Actions > Remove from Hosts. When this action has completed, the parcel button changes to Distribute.
  5. For each activated parcel, select Actions > Delete. This removes the parcel from the local parcel repository.
There might 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.

Delete the Cluster

On the Home page, Click the drop-down list next to the cluster you want to delete and select Delete.

Uninstall the Cloudera Manager Server

The commands for uninstalling the Cloudera Manager Server depend on the method you used to install it. Refer to steps below that correspond to the method you used to install the Cloudera Manager Server.
  • If you used the cloudera-manager-installer.bin file - Run the following command on the Cloudera Manager Server host:
    sudo /usr/share/cmf/uninstall-cloudera-manager.sh
  • 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.
    1. Stop the Cloudera Manager Server and its database:
      sudo service cloudera-scm-server stop
      sudo service cloudera-scm-server-db stop
    2. Uninstall the Cloudera Manager Server and its database. This process described also removes the embedded PostgreSQL database software, if you installed that option. If you did not use the embedded PostgreSQL database, omit the cloudera-manager-server-db steps.

      RHEL systems:

      sudo yum remove cloudera-manager-server
      sudo yum remove cloudera-manager-server-db-2

      SLES systems:

      sudo zypper -n rm --force-resolution cloudera-manager-server
      sudo zypper -n rm --force-resolution cloudera-manager-server-db-2

      Debian/Ubuntu systems:

      sudo apt-get remove cloudera-manager-server
      sudo apt-get remove cloudera-manager-server-db-2

Uninstall Cloudera Manager Agent and Managed Software

Do the following on all Agent hosts:
  1. Stop the Cloudera Manager Agent.
    RHEL 7, SLES 12, Debian 8, Ubuntu 16.04 and higher
    sudo systemctl stop cloudera-scm-supervisord 
    RHEL 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04 or 14.04
    sudo service cloudera-scm-agent hard_stop
  2. Uninstall software:
    OS Parcel Install Package Install
    RHEL
    $ sudo yum remove 'cloudera-manager-*'
    • CDH 5
      $ sudo yum remove 'cloudera-manager-*' avro-tools crunch flume-ng hadoop-hdfs-fuse hadoop-hdfs-nfs3 hadoop-httpfs hadoop-kms hbase-solr hive-hbase hive-webhcat hue-beeswax hue-hbase hue-impala hue-pig hue-plugins hue-rdbms hue-search hue-spark hue-sqoop hue-zookeeper impala impala-shell kite llama oozie pig pig-udf-datafu search sentry solr-mapreduce spark-core spark-master spark-worker spark-history-server spark-python sqoop sqoop2 hue-common oozie-client solr solr-doc sqoop2-client zookeeper
    SLES
    $ sudo zypper remove 'cloudera-manager-*'
    • CDH 5
      $ sudo zypper remove 'cloudera-manager-*' avro-tools crunch flume-ng hadoop-hdfs-fuse hadoop-hdfs-nfs3 hadoop-httpfs hadoop-kms hbase-solr hive-hbase hive-webhcat hue-beeswax hue-hbase hue-impala hue-pig hue-plugins hue-rdbms hue-search hue-spark hue-sqoop hue-zookeeper impala impala-shell kite llama oozie pig pig-udf-datafu search sentry solr-mapreduce spark-core spark-master spark-worker spark-history-server spark-python sqoop sqoop2 hue-common oozie-client solr solr-doc sqoop2-client zookeeper
    Debian/Ubuntu
    $ sudo apt-get purge 'cloudera-manager-*'
    • CDH 5
      $ sudo apt-get purge 'cloudera-manager-*' avro-tools crunch flume-ng hadoop-hdfs-fuse hadoop-hdfs-nfs3 hadoop-httpfs hadoop-kms hbase-solr hive-hbase hive-webhcat hue-beeswax hue-hbase hue-impala hue-pig hue-plugins hue-rdbms hue-search hue-spark hue-sqoop hue-zookeeper impala impala-shell kite llama oozie pig pig-udf-datafu search sentry solr-mapreduce spark-core spark-master spark-worker spark-history-server spark-python sqoop sqoop2 hue-common oozie-client solr solr-doc sqoop2-client zookeeper
  3. Run the clean command:

    RHEL

    sudo yum clean all 

    SLES

    sudo zypper clean 

    Debian/Ubuntu

    sudo apt-get clean 

Remove Cloudera Manager and User Data

Kill Cloudera Manager and Managed Processes

On all Agent hosts, kill any running Cloudera Manager and managed processes:

for u in cloudera-scm flume hadoop hdfs hbase hive httpfs hue impala llama mapred oozie solr spark sqoop sqoop2 yarn zookeeper; do sudo kill $(ps -u $u -o pid=); done

Remove Cloudera Manager Data

If you are uninstalling on RHEL, run the following commands on all Agent hosts to permanently remove 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.

sudo umount cm_processes
sudo rm -Rf /usr/share/cmf /var/lib/cloudera* /var/cache/yum/cloudera* /var/log/cloudera* /var/run/cloudera*

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

Remove User Data

This step permanently removes all user data. To preserve the data, copy it to another cluster using the distcp command before starting the uninstall process. On all Agent hosts, run the following commands:

sudo rm -Rf /var/lib/flume-ng /var/lib/hadoop* /var/lib/hue /var/lib/navigator /var/lib/oozie /var/lib/solr /var/lib/sqoop* /var/lib/zookeeper

Run the following command on each data drive on all Agent hosts (adjust the paths for the data drives on each host):

sudo rm -Rf data_drive_path/dfs data_drive_path/mapred data_drive_path/yarn

Stop and Remove External Databases

If you chose to store Cloudera Manager or user data in an external database, see the database vendor documentation for details on how to remove the databases.