Cloudera Docs

Upgrading Apache Spark 3.3.x (CDS) on 7.1.8 to Spark 3 on 7.3.1

The following steps will help you upgrading from Apache Spark 3.3.0 or 3.3.2 (CDS) on Cloudera Private Cloud 7.1.8 to Spark 3.4.1 on 7.3.1.

Source cluster version Source cluster Spark 2 version Source cluster Spark 3 version Target cluster version Target cluster Spark 3 version Spark 2 used with connectors1
7.1.8 none 3.3.0 or 3.3.2 (CDS) 7.3.1 3.4.1 no

In-place cluster upgrade

  1. Upgrade the Cloudera Manager Server to 7.13.1.0
    1. Back up the Cloudera Manager server databases, working directories, and several other entities. These backups can be used to restore your Cloudera Manager deployment if there are problems during the upgrade.
    2. Upgrade the Cloudera Manager server software on the Cloudera Manager host using package commands from the command line (for example, yum on RHEL systems). Cloudera Manager automates much of this process and is recommend for upgrading and managing your CDH/Cloudera Runtime clusters.
    3. Upgrade the Cloudera Manager agent software on all cluster hosts. The Cloudera Manager upgrade wizard can upgrade the agent software (and, optionally, the JDK), or you can install the agent and JDK software manually. The CDH or Cloudera Runtime software is not upgraded during this process.
    For more information, see Upgrading Cloudera Manager 7.
  2. Cloudera Manager handles deactivation of the SPARK3 parcel. The parcel itself is not removed but deactivated.

Application migration tasks (Spark 3.x to Spark 3.4.1)

Follow the Spark application migration documentation to migrate your Apache Spark Applications from version 3.3.x to 3.4.1
  1. Refactor your Spark application code.

Final steps

After the upgrade and application migration are complete:
  1. Check the status of your clusters.
  2. Perform benchmark testing on your applications. See Spark Application Migration.
1 Oozie, Solr, Phoenix, Hive Warehouse Connector, Spark Schema Registry