Cloudera Docs

Upgrading CDH 6 to CDP Private Cloud Base

High-level upgrade procedures for upgrades from CDH to CDP Private Cloud Base.

Upgrading CDP Private Cloud Base consists of two major steps, upgrading Cloudera Manager and upgrading the cluster. You are not required to upgrade Cloudera Manager and the cluster at the same time, but the versions of Cloudera Manager and the cluster must be compatible. The major+minor version of Cloudera Manager must be equal to or higher than the major+minor version of CDH or Cloudera Runtime.

Workflow

An upgrade from CDH 6 to CDP Private Cloud Base has the following high-level workflow:
  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 Step 1: Getting Started Upgrading Cloudera Manager 6 and Step 1: Getting Started Upgrading a Cluster.
    5. If you have Cloudera Flow Management installed, verify its compatibility with your target CDP version before starting the upgrade process. For. more information, see the Cloudera Flow Management Upgrade and migration paths documentation.
    6. 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.4.4 or higher. After upgrading to Cloudera Manager 7.4.4 or higher, Cloudera Manager can manage upgrading your cluster to a higher version. See Upgrading Cloudera Manager 6.
  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 CDH 6 Cluster.
  7. Perform any needed post-upgrade transition steps for the components deployed in your clusters. See CDH 6 to CDP Private Cloud Base post-upgrade transition steps.

Component Changes in CDP Private Cloud Base 7

YARN Fair Scheduler is being removed.

The YARN Fair Scheduler is being replaced with the YARN Capacity Scheduler. A transition tool will be provided to convert the Fair Scheduler configurations to Capacity Scheduler.

Hive-on-Spark and Hive-on-MapReduce have been removed. Similar functionality is available with Hive-on-Tez.

Pig, Flume, Sentry, and Navigator have been removed.

  • Pig can be replaced with Hive or Spark.

  • Flume has been replaced with Cloudera Flow Management (CFM). CFM is a no-code data ingestion and management solution powered by Apache NiFi. Contact your Cloudera account team for more information about moving from Flume to CFM.

  • Sentry has been replaced with Ranger. A Sentry-to-Ranger policy transition tool is available for CDP Private Cloud Base 7.1 and transitions will be supported when Replication Manager is used to transition Hive tables from CDH to CDP.

  • Navigator has been replaced with Atlas. Navigator lineage data is transferred to Atlas as part of the CDH to CDP Private Cloud Base upgrade process. Navigator audit data is not transferred to Atlas.