Cloudera Docs

Procedure to Rollback between SP or CHF releases of the same Cloudera Base on premises release line

You can perform a rollback from a just installed CHF (Cumulative Hotfix) or SP (Service Pack) release to the previously installed CHF or SP release, provided both releases belong to the same Cloudera Base on premises release line.

Important Limitations

This rollback procedure has the following limitations:

  • You cannot use this document to rollback between different Cloudera Base on premises release lines. For example, you cannot rollback from 7.3.1 to 7.1.9 or 7.1.7.
  • You cannot use this document to rollback between CHF or SP releases of different Cloudera Base on premises release lines. For example, you cannot rollback from 7.3.1 SP1 CHF1 to 7.1.9 SP1 CHF1.
  • You can rollback from 7.1.9 SP1 CHF7 to 7.1.9 SP1 CHF5.
  • You can rollback from 7.1.9 SP2 to 7.1.9 SP1.
  • You can rollback from 7.1.9 SP1 to 7.1.9 (vanilla release).

For further limitations regarding the applicability of the rollback procedure, see Review Limitations.

Terminology Clarification
  • The term “previous CHF or SP release” refers to the CHF or SP release you installed before the current upgrade attempt started. In other words, this release is the rollback target.
  • This document allows you to rollback only to the previous CHF or SP release, not an arbitrary CHF or SP release of the same release line.

To rollback to the previous CHF or SP release, execute the following steps:

  1. Log in to the Cloudera Manager Admin Console.
  2. Click Parcels from the left menu.
  3. Click Parcel Repositories & Network Settings.
  4. In the Remote Parcel Repository URLs section, click the "+" icon and add the previous CHF or SP release’s URL for your Parcel repository.
  5. Click Save & Verify Configuration. A message with the status of the verification appears above the Remote Parcel Repository URLs section. If the URL is not valid, check the URL and enter the correct URL.
  6. After the URL is verified, click Close.
  7. Locate the row in the table that contains the new Cloudera Runtime parcel and click the Download button.
  8. After the download of the new Cloudera Runtime parcel is complete, click the Distribute button.
    Wait for the parcel to be distributed and unpacked before continuing. Cloudera Manager displays the status of the Cloudera Runtime parcel distribution. Click on the status display to view detailed status for each host.
  9. Click Activate. Cloudera Runtime parcels are activated on the cluster.
  10. When the parcel is activated, click the Cloudera Manager logo to return to the home page.
    The cluster is now rolled back to the previous CHF or SP release.
  11. Restore the following databases from the CDH backups.
    Follow the order below and restore only a single service at a time. Stop the service prior to restoring to the database. Start the service after restoring the database.
    • Ranger
    • Ranger KMS
    • Stream Messaging Manager
    • Schema Registry
    • Hue (only if you are downgrading to CDP Private Cloud Base 7.1.7 SP2)

    The steps for backing up and restoring databases differ depending on the database vendor and version you select for your cluster and are beyond the scope of this document.

    See the following vendor resources for more information:
  12. When the parcel is activated, click the Actions menu next to the cluster name and select Post Cloudera Runtime Upgrade.
  13. Restart the cluster: Click the Actions menu and select Restart.