Upgrading a Cloudera Runtime Cluster
Minimum Required Role: Cluster Administrator (also provided by Full Administrator) This feature is not available when using Cloudera Manager to manage Data Hub clusters.
- From Cloudera Runtime to a higher version of Cloudera Runtime.
- Upgrade Cloudera Runtime to maintenance releases.
When you upgrade a cluster, you use Cloudera Manager to upgrade the cluster software across an entire cluster using Cloudera Parcels. Package-based installations are not supported for Cloudera Runtime and CDP Private Cloud Base upgrades. You must transition your CDH clusters to use Parcels before upgrading to CDP Private Cloud Base. See Migrating from Packages to Parcels.
Cluster upgrades update the Hadoop software and other components. You can use Cloudera Manager to upgrade a cluster for major, minor, and maintenance upgrades. The procedures vary depending on the version of Cloudera Manager you are using, the version of the cluster you are upgrading, and the version of Cloudera Runtime you are upgrading to.
Ranger plugins use a local copy of policies (client-side caching), so even if Ranger Admin server is not available during the schema update part of the process, upgrades do not impact Ranger authorization. In addition, Ranger Admin is deployed in active/active mode, so restarts do not impact the API interfaces. Ranger Admin HA will work with or without a load balancer. During Ranger Admin service upgrade, policy creates/updates are not available. This does not impact Ranger authorization since Ranger plugins continue to use the local cache.
- Hive Metastore
- Key Trustee Server
- Kudu – see Orchestrating a rolling restart with no downtime.
- Ranger KMS
- Schema Registry