Cloudera Docs

Step 1: Getting Started Upgrading Cloudera Manager 5

Loading Filters ... 5.16 5.15 5.14 5.13 7.6.7 7.4.4 5.16 5.15 5.14 5.13 7.1.7.2000 7.1.7

Before you upgrade Cloudera Manager, you need to gather some information and review the limitations and release notes. Fill in the My Environment form below to customize your Cloudera Manager upgrade procedures. See the Collect Information section below for assistance in locating the required information.

Collect Information

  1. Log in to the Cloudera Manager Server host. 
    ssh my_cloudera_manager_server_host
  2. Collect the following information about your environment and fill in the form above. This information will be remembered by your browser on all pages in this Upgrade Guide.
    1. The current version of the Operating System:
      lsb_release -a

      Database parameters:

      cat /etc/cloudera-scm-server/db.properties
      ...
com.cloudera.cmf.db.type=mysql
com.cloudera.cmf.db.host=database_hostname:database_port
com.cloudera.cmf.db.name=scm
com.cloudera.cmf.db.user=scm
com.cloudera.cmf.db.password=SOME_PASSWORD
    2. Log in to the Cloudera Manager Admin console and find the following:
      1. The version of Cloudera Manager used in your cluster. Go to Support > About.
      2. The version of the JDK deployed in the cluster. Go to Support > About.

Preparing to Upgrade Cloudera Manager

  • Access to Cloudera Manager binaries for production purposes requires authentication. In order to download the software, you must first have an active subscription agreement and obtain a license key file along with the required authentication credentials (username and password). See Cloudera Manager Download Information.
  • You must have SSH access to the Cloudera Manager server hosts and be able to log in using the root account or an account that has password-less sudo permission for all hosts.
  • Review the following when upgrading to Cloudera Manager 7.1 or higher:

    Cloudera Private Cloud Base Requirements and Supported Versions

  • You may be required to upgrade the operating system before upgrading. See Operating System Requirements to determine operating system support for the version of Cloudera Manager you are upgrading to. Depending on the support, you may need to upgrade the operating system.

    If you must or choose to upgrade to a supported operating system, you must determine whether to upgrade the operating system first or Cloudera Manager first. If the current version of Cloudera Manager and the version you are upgrading to both support a newer version of the operating system but the new version of Cloudera Manager does not support the older operating system, you must upgrade to the newer operating system before upgrading Cloudera Manager. If this is not true, then you must upgrade Cloudera Manager before upgrading the operating system.

    See Upgrading the Operating System.

  • Install a supported version of the Java Development Kit (JDK) on all hosts. If you are upgrading to Cloudera Manager and CDP Private Cloud Base 7.1.1 and higher, you can choose to install OpenJDK 1.8 instead of the Oracle JDK.
    There two options for JDK installation:
    • Manually install the Oracle JDK or OpenJDK on all hosts.
    • Manually install the Oracle JDK 1.8 on the Cloudera Manager host, and then select the Install Oracle Java SE Development Kit checkbox when prompted while running the Cloudera Manager Upgrade wizard.

    See Upgrading the JDK

  • Review the Release Notes.
  • Review the Cloudera Security Bulletins.
  • The embedded PostgreSQL database installed with the Trial Installer is not supported in production environments because a trial installation cannot easily be upgraded, backed up, or migrated into a production-ready configuration without manual steps requiring down time.

    Consider migrating from the Cloudera Manager embedded PostgreSQL database server to an external PostgreSQL database before upgrading Cloudera Manager.

  • If your cluster uses Oracle for any databases, before upgrading CDH 5, check the value of the COMPATIBLE initialization parameter in the Oracle Database using the following SQL query: 
    SELECT name, value FROM v$parameter WHERE name = 'compatible'
    The default value is 12.2.0. If the parameter has a different value, you can set it to the default as shown in the Oracle Database Upgrade Guide.

Using Python 3.8 with the Cloudera Manager Agents

If you require Python 3.8 to be used on your cluster hosts, you must install Python 3.8 before you upgrade Cloudera Manager. See Installing Python 3.8 for Cloudera Manager 7.7.3

Important: Cloudera Manager 7.7.3 should only be used when you need to use Python 3.8 for the Cloudera Manager agents. You must install Python 3.8 on all hosts before installing or upgrading to Cloudera Manager 7.7.3. Cloudera Manager 7.7.3 is only supported with RHEL 7.9 . 8.4, and 8.6 . See the CDP Private Cloud Base Installation guide for more information.

Using Python 3 with the Cloudera Manager Agents

You must install Python 3 on all hosts before upgrading to Cloudera Manager 7.11.3. See Installing Python 3.

Using Python 3 with the Cloudera Manager Agents

You must install Python 3 on all hosts before upgrading to Cloudera Manager 7.13.1. See Installing Python 3.

Migrating from Python 3.8 to Python 3.9 on RHEL 8.8 or RHEL 8.10

Cloudera recommends you to install Python 3.9 before upgrading Cloudera Manager to 7.13.1 version to ensure smooth transition with minimal downtime.

(Recommended) Installing Python 3.9 on RHEL 8 before upgrading Cloudera Manager to 7.13.1 and CDP Runtime to 7.3.1
Learn how to migrate Cloudera Manager and CDP Runtime from Python 3.8 to Python 3.9 on RHEL 8.8 or RHEl 8.10. This is the recommended workflow for customers upgrading Cloudera Manager to 7.13.1 version and CDP Runtime to 7.3.1 version since the minimum recommended version of Python is now 3.9.
  1. Install Python 3.9 from standard repository. For information about installing Python 3.9 on RHEL 8, see Installing Python 3.9 standard package on RHEL 8.
  2. Upgrade Cloudera Manager to 7.13.1 version. For information about upgrading Cloudera Manager, see Upgrading Cloudera Manager 7.
  3. Upgrade CDP Runtime to 7.3.1 version. For information about upgrading Cloudera Runtime Cluster, see Upgrading a Cloudera Runtime Cluster.
  4. Uninstall Python 3.8. To uninstall Python 3.8 run the following command:
    yum remove python38
(Not Recommended) Installing Python 3.9 on RHEL 8 after upgrading Cloudera Manager to 7.13.1 and CDP Runtime to 7.3.1
Learn how to upgrade Cloudera Manager and CDP Runtime while delaying the upgrade of Python from 3.8 to 3.9 version on RHEL 8.8 or RHEL 8.10. This is not a recommended workflow due to Hue supports only Python 3.9 in CDP Runtime 7.3.1.
  1. Upgrade Cloudera Manager to 7.13.1 version. For information about upgrading Cloudera Manager, see Upgrading Cloudera Manager 7.
  2. Upgrade CDP Runtime to 7.3.1 version. For information about upgrading Cloudera Runtime Cluster, see Upgrading a Cloudera Runtime Cluster.
  3. Install Python 3.9 from standard repository. For information about installing Python 3.9 on RHEL 8, see Installing Python 3.9 standard package on RHEL 8.
  4. Restart Cloudera Manager Agents. For information about restarting Cloudera Manager Agents, see Starting, Stopping, and Restarting Cloudera Manager Agents.

    After restarting Cloudera Manager Agents, Cloudera Manager Agent will pick up the highest Python version available between Python 3.8 and Python 3.9.

  5. Resart all CDP Runtime services so that they will pick up the Python 3.9 version. To restart all CDP Runtime services, restart the cluster. For information about restarting a cluster, see Restarting a Cluster.
  6. Uninstall Python 3.8. To uninstall Python 3.8 run the following command:
    yum remove python38

When Cloudera Manager is upgraded to 7.13.1 version and when CDP Runtime is either 7.1.8, 7.1.7 SP3 or 7.1.9 for RHEL8, all the CDP Runtime process will continue to use Python 3.8, whereas Cloudera Manager Agent will pick up the highest Python version available between Python 3.8 and Python 3.9.