Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to use CDH uninstall based on CM installation

2025-01-22 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)05/31 Report--

This article focuses on "how to use CDH uninstall based on CM installation". Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to use CDH uninstall based on CM installation.

1. Uninstall CM: (CM host executes) 1. Remove all service 


First stop all component services of the cluster on the Cloudera Manager management side, and then delete all services.

2. Delete Manager Server (always select yes. Uninstall did not perform step 3 successfully)

Execute the following command on the host where CM is installed, requiring root permission:

Sudo/usr/share/cmf/uninstall-cloudera-manager.sh

3. If the script is not available, you can delete it manually and stop the service first:

The command is as follows:

Sudo service cloudera-scm-server stop

Sudo service cloudera-scm-server-db stop

Sudo yum remove cloudera-manager-server

Sudo yum remove cloudera-manager-server-db

Uninstall CDH: (execute by all hosts) 1. Delete CDH services on all CDH nodes

Sudo service cloudera-scm-agent hard_stop

2. Uninstall the rpm package of cloudera

View:

Rpm-qa | grep cloudera

Delete them one by one:

For f in `rpm-qa | grep cloudera `; do rpm-e ${f}; done

Sudo yum remove 'cloudera-manager-*' hadoop hue-common' bigtop-*'

3. Delete the installation directory of cloudera

Sudo rm-rf / usr/share/cmf / var/lib/cloudera* / var/cache/yum/x86_64/6/cloudera* / var/log/cloudera* / var/run/cloudera*

* * if a file occupation error is reported, restart the machine and execute the command immediately

Database configuration:

Rm-rf / etc/cloudera*

4. Clean up Cloudera related files

The command is as follows:

Sudo rm-rf / var/lib/flume-ng / var/lib/hadoop* / var/lib/hue / var/lib/oozie / var/lib/solr / var/lib/sqoop*

Sudo rm-rf / dfs / mapred / yarn

Rm-rf / var/run/hadoop* / var/run/flume-ng* / var/run/cloudera* / var/run/oozie* / var/run/sqoop* / var/run/zookeeper* / var/run/hbase* / var/run/impala* / var/run/hive* / var/run/hdfs-sockets

Rm-rf / usr/lib/hadoop / usr/lib/hadoop* / usr/lib/hive / usr/lib/hbase / usr/lib/oozie / usr/lib/sqoop* / usr/lib/zookeeper / usr/lib/bigtop* / usr/lib/flume-ng / usr/lib/hcatalog

Rm-rf / usr/bin/hadoop* / usr/bin/zookeeper* / usr/bin/hbase* / usr/bin/hive* / usr/bin/hdfs / usr/bin/mapred / usr/bin/yarn / usr/bin/sqoop* / usr/bin/oozie

Rm-rf / etc/hadoop* / etc/zookeeper* / etc/hive* / etc/hue / etc/impala / etc/sqoop* / etc/oozie / etc/hbase* / etc/hcatalog

5. Clear the configuration under the alternatives directory

The command is as follows:

Rm-rf / etc/alternatives/flume*

Rm-rf / etc/alternatives/hadoop*

Rm-rf / etc/alternatives/hbase*

Rm-rf / etc/alternatives/hive*

Rm-rf / etc/alternatives/hue*

Rm-rf / etc/alternatives/impala*

Rm-rf / etc/alternatives/llama*

Rm-rf / etc/alternatives/oozie*

Rm-rf / etc/alternatives/pig*

Rm-rf / etc/alternatives/solr*

Rm-rf / etc/alternatives/spark*

Rm-rf / etc/alternatives/sqoop*

Rm-rf / etc/alternatives/zookeeper*

6. Erase the data from the previous version (the old version is 4.* the directory needs to be deleted)

The command is as follows:

Rm-rf / var/lib/alternatives/ {cdh.app}

Rm-rf / var/lib/alternatives/flume*

Rm-rf / var/lib/alternatives/hadoop*

Rm-rf / var/lib/alternatives/hbase*

Rm-rf / var/lib/alternatives/hive*

Rm-rf / var/lib/alternatives/hue*

Rm-rf / var/lib/alternatives/impala*

Rm-rf / var/lib/alternatives/llama*

Rm-rf / var/lib/alternatives/oozie*

Rm-rf / var/lib/alternatives/pig*

Rm-rf / var/lib/alternatives/solr*

Rm-rf / var/lib/alternatives/spark*

Rm-rf / var/lib/alternatives/sqoop*

Rm-rf / var/lib/alternatives/zookeeper*

7. Delete logs and cache data directories

The command is as follows:

Tmpwatch-afv 1 / tmp

Rm-rf / opt/cloudera/*

Rm-rf / var/log/hadoop-*

Rm-rf / var/log/hue*

Rm-rf / var/log/oozie*

Rm-rf / var/log/sqoop*

Rm-rf / var/log/pig*

Rm-rf / var/log/hive*

Rm-rf / var/log/hbase*

Rm-rf / var/log/zookeeper*

Rm-rf / var/log/mahout*

Rm-rf / var/log/impala*

Rm-rf / var/log/hdfs*

Rm-rf / var/lib/hdfs*

Rm-rf / var/lib/alternatives/hdfs*

Rm-rf / var/run/hdfs*

Rm-rf / etc/hdfs*

Rm-rf / etc/alternatives/hdfs*

Rm-rf / usr/bin/hdfs*

Rm-rf / var/run/hdfs*

Rm-rf / var/log/yarn*

Rm-rf / var/log/whirr*

Rm-rf / var/log/mapred*

Rm-rf / var/lib/mapred*

Rm-rf / var/lib/alternatives/mapred*

Rm-rf / var/run/mapred*

Rm-rf / etc/mapred*

Rm-rf / etc/alternatives/mapred*

Rm-rf / usr/bin/mapred*

Rm-rf / var/run/mapred*

8. Kill the related process

For u in hdfs mapred cloudera-scm hbase hue zookeeper oozie hive impala flume spark; do sudo kill $(ps-u $u-o pid=); done

9. Delete the lock file of Cloudera Manager

Sudo rm / tmp/.scm_prepare_node.lock

10. Delete parcel package distribution files and extract files

Rm-rf / opt/cloudera/parcel-cache / opt/cloudera/parcels

At this point, I believe you have a better understanding of "how to use CDH uninstall based on CM installation". You might as well do it in practice! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report