After You Upgrade Cloudera Manager

Minimum Required Role: Cluster Administrator (also provided by Full Administrator)

Loading Filters ... 6.3.4 6.3.3 6.3.1 6.3.0 6.2.1 6.2.0 6.1.1 6.1.0 6.0.1 6.0.0 5.16 5.15 5.14 5.13 5.12 5.11 5.10 5.9 5.8 5.7 5.6 5.5 5.4 5.3 5.2 5.1 5.0 6.3.4 6.3.3 6.3.2 6.2.1 6.2.0 6.1.1 6.1.0 6.0.1 6.0.0 5.16 5.15 5.14 5.13 5.12 5.11 5.10 5.9 5.8 5.7 5.6 5.5 5.4 5.3 5.2 5.1 5.0

Upgrade Cloudera Navigator Encryption Components

Upgrade any Cloudera Navigator Encryption components deployed in your cluster:

  • Cloudera Navigator Key Trustee Server
  • Cloudera Navigator Key HSM
  • Cloudera Navigator Key Trustee KMS
  • Cloudera Navigator Encrypt.

If you are still using Key Trustee Server 5.4, and you are upgrading to Cloudera Manager 5.10 or higher, you must upgrade the Key Trustee Server to a more recent version.

You can upgrade other Cloudera Navigator components at any time. You do not have to perform these upgrades when upgrading Cloudera Manager or CDH.

See Upgrading Cloudera Navigator Data Encryption.

Perform Post Upgrade Steps

  1. If you upgraded the JDK, do the following:
    1. If the Cloudera Manager Server host is also running a Cloudera Manager Agent, restart the Cloudera Manager Server:
    2. Restart the Cloudera Manager Server.
      RHEL 7, SLES 12, Debian 8, Ubuntu 16.04 and higher
      sudo systemctl restart cloudera-scm-server
      RHEL 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04 or 14.04
      sudo service cloudera-scm-server restart
    3. Open the Cloudera Manager Admin Console and set the Java Home Directory property in the host configuration:
      1. Go to Home > All Hosts > Configuration.
      2. Set the value to the path to the new JDK.
      3. Click Save Changes.
    4. Restart all services:
      1. On the Home > Status tab, click next to the cluster name, select Restart and confirm.
  2. Start the Cloudera Management Service and adjust any configurations when prompted.
    1. Log in to the Cloudera Manager Admin Console.
    2. Select Clusters > Cloudera Management Service.
    3. Select Actions > Start.
  3. If Cloudera Manager reports stale configurations after the upgrade, you might need to restart the cluster services and redeploy the client configurations. If you are also upgrading CDH, this step is not required.
    Stale configurations can occur after a Cloudera Manager upgrade when a default configuration value has changed, which is often required to fix a serious problem. Configuration changes that result in Cloudera Manager reporting stale configurations are described the release notes:
    1. On the Home > Status tab, click next to the cluster name, select Restart and confirm.
    2. On the Home > Status tab, click next to the cluster name, select Deploy Client Configuration and confirm.
  4. If upgrading from Navigator 2.6 (Cloudera Manager 5.7) or lower:
    1. Start and log into the Cloudera Navigator data management component UI. The Upgrading Navigator page displays. Depending on the amount of data in the Navigator Metadata Server storage directory, the upgrade process can take three to four hours or longer.

    When the upgrade is complete, click Continue. The Cloudera Navigator landing page is displayed.

  5. If you disabled any backup or snapshot jobs before the upgrade, now is a good time to re-enable them
  6. If you deleted any Hive Replication schedules before the Cloudera Manager upgrade, re-create them now.
  7. The Cloudera Manager upgrade is now complete. If Cloudera Manager is not working correctly, or the upgrade did not complete, see Troubleshooting a Cloudera Manager Upgrade.