Deleting an unregistered classic cluster

If you started registering an on-prem cluster in Cloudera on cloud using Cluster Connectivity Manager v1 and have not yet completed it, we recommend that you delete the unregistered cluster and re-register it using Cluster Connectivity Manager v2.

Classic clusters that are already registered with Cluster Connectivity Manager v1 continue to use Cluster Connectivity Manager v1, but new cluster registrations should be using Cluster Connectivity Manager v2. If you started registering an on-prem cluster in Cloudera on cloud using Cluster Connectivity Manager v1 and have not yet completed it, we recommend that you delete the unregistered cluster and re-register it using Cluster Connectivity Manager v2. We suggest this as it will save the future efforts required to upgrade from Cluster Connectivity Manager v1 to Cluster Connectivity Manager v2.

Steps

If you reached step 2 or 3 in classic cluster registration, you should first stop the Cluster Connectivity Manager tunnel and then clean up the setup files that you must have downloaded for Cluster Connectivity Manager v1. Run the following commands on the Cloudera Manager host (CDH or Cloudera Base on premises cluster) or on the KNOX host (HDP cluster).
1. Check the tunnel status:
```
systemctl status ccm-tunnel@CM.service
```
2. Use below commands to stop tunnel and cleanup Cluster Connectivity Manager v1 resources:
  - CentOS7/RHEL7:
    CDH or Cloudera Base on premises cluster
    systemctl stop ccm-tunnel@CM.service yum remove autossh
    HDP cluster
    systemctl stop ccm-tunnel@KNOX.service yum remove autossh
  - CentOS6/RHEL6:
    CDH or Cloudera Base on premises cluster
```
service reverse-tunnel stop 'CM'
yum remove autossh
```
    HDP cluster
```
service reverse-tunnel stop 'KNOX'
yum remove autossh
```
Delete the cluster from the classic cluster UI by clicking on the context menu next to the cluster name and selecting Remove.
Enter the cluster name and click Remove.