Before upgrading to higher versions of CDH and transitioning to CDP Private Cloud Base, you must understand the types of upgrades so that you can make an informed decision about the target release version. Reviewing the new features and changes in the target release enables you to understand the upgrade requirements.

Before beginning your upgrade, review the list of supported upgrade paths to ensure that the upgrade you are planning is supported. Upgrades are not supported between all versions of Cloudera Manager, CDH, or Cloudera Runtime. See Supported Upgrade Paths.

About the online Upgrade Guide

This online version of the Cloudera Upgrade Guide allows you to create a customized version of the guide that only includes the steps required for your upgrade. Use the form at the top of pages in this guide to select the Cloudera Manager, CDH or Cloudera Runtime version for your upgrade as well as the operating system version, database type, and other information about your upgrade. After making these selections, the pages in the guide will only include the required steps for your upgrade. The information you enter is retained on each page in the guide.

Upgrading to CDP Private Cloud Base

An upgrade from Cloudera Manager and CDH to CDP Private Cloud Base consists of the following high-level steps:
  1. Prepare to upgrade:
    1. Review the Supported Upgrade Paths for your upgrade.
    2. Review the Requirements and Supported Versions for your upgrade
    3. Review the Release Notes for the version of CDP Private Cloud Base you are upgrading to.
    4. Gather information on your deployment. See Getting Started Upgrading Cloudera Manager and Getting Started Upgrading a Cluster.
    5. Plan how and when to begin your upgrade.
  2. If necessary, Upgrade the JDK.
  3. If necessary, Upgrade the Operating System.
  4. Perform any needed pre-upgrade transition steps for the components deployed in your clusters. See CDP Private Cloud Base Pre-upgrade transition steps
  5. Upgrade Cloudera Manager to version 7.1.1 or higher. After upgrading to Cloudera Manager 7.1.1 or higher, Cloudera Manager can manage upgrading your cluster to a higher version. See Upgrading Cloudera Manager.
  6. Use Cloudera Manager to Upgrade CDH to Cloudera Runtime 7, or from Cloudera Runtime to a higher version of Cloudera Runtime. See Upgrading a Cluster.
  7. Perform any needed post-upgrade transition steps for the components deployed in your clusters. See CDH to CDP Private Cloud Base post-upgrade transition steps.

Assessing the Impact of an Upgrade

Plan for a sufficient maintenance window to perform an upgrade. Depending on which components you are upgrading, the number of hosts in your cluster, and the type of hardware, you might need up to a full day to upgrade your cluster. Before you begin the upgrade, you need to gather some information; these steps are also detailed in the Cloudera Manager and CDH upgrade procedures.

Before upgrading, consult the release notes for Cloudera Manager and CDH to learn about API changes, deprecated features, new features, and incompatible changes.

Also check the following pages to make sure that you are using a supported operating system, JDK, database, and other components:
There are three types of upgrades: major, minor, and maintenance:
Major Upgrades
Major upgrades include the following:
  • From Cloudera Manager 5.x and CDH 5.x to Cloudera Manager and Cloudera Runtime 7.1.1 or higher
  • From Cloudera Manager and Cloudera Runtime 7.0.3 to Cloudera Manager and Cloudera Runtime 7.1.1 (CDP Private Cloud Base)
  • From Cloudera Manager 6.x to Cloudera Manager 7.1.1
A major upgrade typically has the following characteristics:
  • Large changes to functionality and update of Hadoop to a more recent version
  • Incompatible changes in data formats
  • Significant changes and additions to the user interface in Cloudera Manager
  • Database schema changes for Cloudera Manager that are automatically handled by the upgrade process
  • Significant down time is required to upgrade the cluster.
  • Client Configurations are redeployed.
Minor Upgrades
Minor upgrades upgrade your software to a higher minor version of a major release—for example from version 6.0.0 to version 6.1.0—and typically include the following:
  • New functionality
  • Bug fixes
  • Potential database schema changes for Cloudera Manager that are handled automatically
  • Client Configurations are redeployed.
Incompatible changes or changes to data formats are generally not introduced in minor upgrades.
Maintenance Upgrades

Maintenance upgrades fix critical bugs or address security issues. The version numbers for maintenance releases differ only in the third digit, for example, when upgrading from version 6.0.0 to 6.0.1.

To upgrade to a maintenance release, you only need to perform a subset of the Minor version upgrade steps. Follow the same procedures as for minor version upgrades but skip the steps that are labeled as follows: