Upgrading a classic cluster from CCMv1 to CCMv2

Existing classic clusters (CDH, HDP, or Cloudera Private Cloud Base) registered in Cloudera Public Cloud’s Management Console with Cloudera Private Cloud Base v1 (CCMv1) should be upgraded to use CCMv2.

Prior to upgrading, open ports for CCMv2. If you would like to use Cluster Connectivity Managerv2 (CCMv2), ensure that outgoing traffic is allowed on port 443 on the legacy CDH, HDP, or Cloudera Private Cloud Base cluster.

  1. Log in to the Cloudera web interface.
  2. Navigate to the Cloudera Management Console.
  3. From the left navigation pane, select Classic clusters.
  4. Find your previously registered classic cluster.
  5. If your cluster need to be upgraded, you will see the icon next to its name. After clicking on this icon, you will see the Upgrade Now button, as shown in the following screenshot:
  6. Click the Upgrade Now button to start the upgrade process.
  7. Information about three upgrade steps is displayed:
  8. Cloudera automatically starts step 1. It normally takes 2-4 minutes. Once step 1 is marked as Completed, you can proceed to step 2.
  9. In step 2:
    1. Click on Files.
    2. On the Setup Connectivity Client page, select the operating system of your cluster.
    3. Download the files mentioned under Files.
    4. Follow the installation steps described under How to Install. You will need to SSH to the host mentioned in these instructions and run the commands.
    5. Once done, click Close.
    6. Click on Test Connection.
    7. Once the connection is successful, step 2 is marked as Completed. You can proceed to step 3.
  10. In step 3:
    1. Click on Switch.
    2. A pop-up window appears with instructions on how to clean up CCMv1 resources. Under Select OS, select your operating system and then follow the cleanup steps described for your cluster type. You need to SSH to the specific cluster node indicated in the instructions in order to perform the cleanup. The steps that you need to perform are as follows (The same steps are printed in the UI):
      • Centos7/RHEL7

        On a CDH or Cloudera Private Cloud Base cluster, run the following on the Cloudera Manager host:

        systemctl stop ccm-tunnel@CM.service
        yum remove autossh

        On an HDP cluster, run the following on the KNOX host:

        systemctl stop ccm-tunnel@KNOX.service
        yum remove autossh
      • Centos6/RHEL6

        On a CDH or Cloudera Private Cloud Base cluster, run the following on the Cloudera Manager host:

        service reverse-tunnel stop 'CM'
        yum remove autossh

        On an HDP cluster, run the following on the KNOX host:

        service reverse-tunnel stop KNOX
        yum remove autossh
  11. Once your cluster has been upgraded the icon appears next to its name.
  12. From the ICON menu of the upgraded cluster select Refresh to synchronize the cluster with Cloudera:
  13. The cluster status changes to Active.

Once you have performed the upgrade, you can continue using your cluster as usual.