Cloudera Docs

Upgrading a Cluster

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

This topic describes how to upgrade a CDH or cluster in any of the following scenarios:
  • From to a higher version of .
  • Upgrade to maintenance releases.

When you upgrade a cluster, you use to upgrade the cluster software across an entire cluster using Parcels. Package-based installations are not supported for and upgrades. You must transition your CDH clusters to use Parcels before upgrading to . See Migrating from Packages to Parcels.

Cluster upgrades update the Hadoop software and other components. You can use to upgrade a cluster for major, minor, and maintenance upgrades. The procedures vary depending on the version of you are using, the version of the cluster you are upgrading, and the version of 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.

After completing preparatory steps, you use the upgrade wizard to complete the upgrade. will restart all services after the upgrade. Services that support rolling restart will be restarted in a rolling fashion that does not require you to take the services offline during the upgrade. All other services will be restarted normally. The following services support rolling restart: