1. On the host running the Cloudera Manager Server, stop the Cloudera Manager Server:

   $ sudo service cloudera-scm-server stop

2. If you are using the embedded PostgreSQL database for Cloudera Manager, stop the database:

   $ sudo service cloudera-scm-server-db stop

     Important: If you are not running the embedded database service and you attempt to stop it, you will get a message to the effect that the service cannot be found. If instead you get a message that the shutdown failed, this means the embedded database is still running, probably due to services connected to the Hive Metastore. Do not proceed with the installation until you have stopped all your Metastore-dependent services and the database successfully shuts down (restart the Cloudera Manager server to shut down services as necessary). If you continue without solving this, your upgrade will fail and you will be left with a non-functional Cloudera Manager installation.
3. If the Cloudera Manager host is also running the Cloudera Manager Agent, stop the Cloudera Manager Agent:

   $ sudo service cloudera-scm-agent stop

If you are manually upgrading the Cloudera Manager Agent packages in Upgrade Cloudera Manager Agent Packages, and you plan to upgrade to CDH 5, install JDK1.7u45 on the Agent hosts following the instructions in Java Development Kit Installation.

If you are not running Cloudera Manager Server on the same host as a Cloudera Manager Agent, and you want all hosts to run the same JDK version, optionally install JDK1.7u45 on that host.

1. To upgrade the Cloudera Manager Server Packages, you can upgrade from Cloudera's repository at http://archive.cloudera.com/cm5/ or you can create your own repository, as described in Understanding Custom Installation Solutions. Creating your own repository is necessary if you are upgrading a cluster that does not have access to the Internet.
   1. Find the Cloudera repo file for your distribution by starting at http://archive.cloudera.com/cm5/ and navigating to the directory that matches your operating system.

      For example, for Red Hat or CentOS 6, you would navigate to http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/. Within that directory, find the repo file that contains information including the repository's base URL and GPG key. The contents of the cloudera-manager.repo file might appear as follows:

      [cloudera-manager]
      # Packages for Cloudera Manager, Version 5, on RedHat or CentOS 6 x86_64
      name=Cloudera Manager
      baseurl=http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/5/
      gpgkey = http://archive.cloudera.com/cm5/redhat/6/x86_64/cm/RPM-GPG-KEY-cloudera
      gpgcheck = 1

      For Ubuntu or Debian systems, the repo file can be found by navigating to the appropriate release directory, for example, http://archive.cloudera.com/cm4/debian/wheezy/amd64/cm. The repo file, in this case, cloudera.list, may appear as follows:

      # Packages for Cloudera Manager, Version 5, on Debian 7.0 x86_64
      deb http://archive.cloudera.com/cm5/debian/wheezy/amd64/cm wheezy-cm5 contrib
      deb-src http://archive.cloudera.com/cm5/debian/wheezy/amd64/cm wheezy-cm5 contrib

   2. Replace the repo file in the configuration location for the package management software for your system.

      Operating System	Commands
      RHEL	Copy cloudera-manager.repo to /etc/yum.repos.d/.
      SLES	Copy cloudera-manager.repo to /etc/zypp/repos.d/.
      Ubuntu or Debian	Copy cloudera.list to /etc/apt/sources.list.d/.

   3. Run the following commands:

      Operating System	Commands
      RHEL	$ sudo yum clean all $ sudo yum upgrade 'cloudera-*'   Note: yum clean all cleans up yum's cache directories, ensuring that you download and install the latest versions of the packages If your system is not up to date, and any underlying system components need to be upgraded before this yum update can succeed. yum will tell you what those are.
      SLES	$ sudo zypper clean --all $ sudo zypper up -r http://archive.cloudera.com/cm5/sles/11/x86_64/cm/5/ To download from your own repository: $ sudo zypper clean --all $ sudo zypper rr cm $ sudo zypper ar -t rpm-md http://myhost.example.com/<path_to_cm_repo>/cm $ sudo zypper up -r http://myhost.example.com/<path_to_cm_repo>
      Ubuntu or Debian	Use the following commands to clean cached repository information and update Cloudera Manager components: $ sudo apt-get clean $ sudo apt-get update $ sudo apt-get dist-upgrade $ sudo apt-get install cloudera-manager-server cloudera-manager-agent cloudera-manager-daemons As this process proceeds, you may be prompted concerning your configuration file version: Configuration file `/etc/cloudera-scm-agent/config.ini' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. You will receive a similar prompt for /etc/cloudera-scm-server/db.properties. Answer N to both these prompts. The config.ini file should be carefully inspected and the files merged together to ensure the new entries are incorporated.

$ rpm -qa 'cloudera-manager-*'
cloudera-manager-agent-5.0.7-0.cm5.p0.932.el6.x86_64
cloudera-manager-server-5.0.7-0.cm5.p0.932.el6.x86_64
cloudera-manager-daemons-5.0.7-0.cm5.p0.932.el6.x86_64

~# dpkg-query -l 'cloudera-manager-*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                   Version                Description
+++-======================-======================-============================================================
ii  cloudera-manager-agent 5.0.7-0.cm5.p0.932~sq The Cloudera Manager Agent
ii  cloudera-manager-daemo 5.0.7-0.cm5.p0.932~sq Provides daemons for monitoring Hadoop and related tools.
ii  cloudera-manager-serve 5.0.7-0.cm5.p0.932~sq The Cloudera Manager Server  

  Important: All hosts in the cluster must have access to the Internet if you plan to use archive.cloudera.com as the source for installation files. If you do not have Internet access, create a custom repository.

1. Log in to the Cloudera Manager Admin Console.
2. Upgrade hosts using one of the following methods:
   • Cloudera Manager installs Agent software
     1. Select Yes, I would like to upgrade the Cloudera Manager Agent packages now and click Continue.
     2. Select the release of the Cloudera Manager Agent to install. Normally, this will be the Matched Release for this Cloudera Manager Server. However, if you used a custom repository (that is, a repository other than archive.cloudera.com) for the Cloudera Manager server, select Custom Repository and provide the required information. The custom repository allows you to use an alternative location, but that location must contain the matched Agent version. Click Continue to proceed to the Configure Java Encryption screen.
     3. ​If local laws permit you to deploy unlimited strength encryption, and you want to run a secure cluster, check the Install Java Unlimited Strength Encryption Policy Files checkbox to install unlimited strength policy files for Java. This is required because during upgrade Cloudera Manager installs a copy of the Java 7 JDK, which does not include the unlimited strength policy files. Click Continue to proceed to the Upgrade Cloudera Manager Agent Packages screen.
     4. Specify credentials and initiate Agent installation:
        1. Select root or enter the user name for an account that has password-less sudo permission.
        2. Select an authentication method:
           • If you choose to use password authentication, enter and confirm the password.
           • If you choose to use public-key authentication provide a passphrase and path to the required key files.
        3. You can choose to specify an alternate SSH port. The default value is 22.
        4. You can specify the maximum number of host installations to run at once. The default value is 10.
     5. Click Continue. The Cloudera Manager Agent packages are installed.
   • Manually install Agent software. On all cluster hosts except the Cloudera Manager server host:
     1. Select No, I would like to skip the agent upgrade now and click Continue.
     2. Copy the appropriate repo file as described in step 3 of Upgrade Cloudera Manager Server Packages.
     3. Run the following commands:

        Operating System	Commands
        RHEL	$ sudo yum clean all $ sudo yum upgrade 'cloudera-*'   Note: yum clean all cleans up yum's cache directories, ensuring that you download and install the latest versions of the packages If your system is not up to date, and any underlying system components need to be upgraded before this yum update can succeed. yum will tell you what those are.
        SLES	$ sudo zypper clean --all $ sudo zypper up -r http://archive.cloudera.com/cm5/sles/11/x86_64/cm/5/ To download from your own repository: $ sudo zypper clean --all $ sudo zypper rr cm $ sudo zypper ar -t rpm-md http://myhost.example.com/<path_to_cm_repo>/cm $ sudo zypper up -r http://myhost.example.com/<path_to_cm_repo>
        Ubuntu or Debian	Use the following commands to clean cached repository information and update Cloudera Manager components: $ sudo apt-get clean $ sudo apt-get update $ sudo apt-get dist-upgrade $ sudo apt-get install cloudera-manager-agent cloudera-manager-daemons As this process proceeds, you may be prompted concerning your configuration file version: Configuration file `/etc/cloudera-scm-agent/config.ini' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. You will receive a similar prompt for /etc/cloudera-scm-server/db.properties. Answer N to both these prompts. The config.ini file should be carefully inspected and the files merged together to ensure the new entries are incorporated.

     4. If local laws permit you to deploy unlimited strength encryption, and you want to run a secure cluster, install the unlimited strength JCE policy files. This is required because during upgrade Cloudera Manager installs a copy of the Java 7 JDK, which does not include the unlimited strength policy files.
3. Click Continue. The Host Inspector runs to inspect your managed hosts for correct versions and configurations. If there are problems, you can make changes and then re-run the inspector. When you are satisfied with the inspection results, click Continue and then click Finish.
4. If you are upgrading from a free version of Cloudera Manager prior to 4.6, click Continue to assign the Cloudera Management Services roles to hosts.
5. If you are upgrading from a free version of Cloudera Manager prior to 4.6 to Cloudera Enterprise, specify required databases:
   1. Configure settings for required databases:
      1. Choose the database type:
         • Leave the default setting of Use Embedded Database to have Cloudera Manager create and configure all required databases. Make a note of the auto-generated passwords.
         • Select Use Custom Databases to specify external databases. Enter the database host, database type, database name, username, and password for the databases that you created when you set up databases for Cloudera Manager.
           1. Provide information for the Activity Monitor (only needed when using MapReduce), Reports Manager, and Hive Metastore, and Cloudera Navigator databases. The value you enter as the database hostname must match the value you entered for the hostname (if any) when you created the database.
      2. Click Test Connection to confirm that Cloudera Manager can communicate with the databases using the information you have supplied. If the test succeeds in all cases, click Continue; otherwise check and correct the information you have provided for the databases and then try the test again. (For Hive, if you are using the embedded database, you will see a message saying the database will be created at a later point in the installation process.) The Review Changes page displays.
6. Review the configuration changes to be applied. Confirm the settings entered for file system paths. The file paths required vary based on the services to be installed. For example, you might confirm the NameNode Data Directory and the DataNode Data Directory for HDFS.
     Warning: DataNode data directories should not be placed on NAS devices.
   Click Continue. The wizard starts the services.
7. Click Finish. If you are upgrading from Cloudera Manager prior to 4.5:
   1. Select the host for the Hive Metastore Server role.
   2. Review the configuration values and click Accept to continue.
        Note:

      • If Hue was using a Hive Metastore backed by a Derby database, then the newly created Hive Metastore Server will also use Derby. Since Derby does not allow concurrent connections, Hue will continue to work, but the new Hive Metastore Server will fail to run. The failure is harmless (because nothing uses this new Hive Metastore Server at this point) and intentional, to preserve the set of cluster functionality as it was before upgrade. Cloudera discourages the use of a Derby backed Hive Metastore due to its limitations. You should consider switching to a different supported database.
      • Prior to Cloudera Manager 4.5, Hue and Impala connected directly to the Hive Metastore database, so the bypass mode is enabled by default when upgrading to Cloudera Manager 4.5 or later. This is to ensure the upgrade doesn't disrupt your existing setup. You should plan to disable the bypass mode, especially when using CDH 4.2 or later. Using the Hive Metastore Server is the recommended configuration and the WebHCat Server role requires the Hive Metastore Server to not be bypassed. To disable bypass mode, see Disabling Bypass Mode. After changing this configuration, you must re-deploy your client configurations, restart Hive, and restart any Hue or Impala services configured to use that Hive.
      • If you are using CDH 4.0 or CDH 4.1, see known issues related to Hive in Known Issues and Workarounds in Cloudera Manager 5.
8. If you are upgrading from Cloudera Manager prior to 4.8, select where the Impala Catalog Server role will run.

All services (except for the services you stopped in Stop Selected Services) should be running.

Because Cloudera Manager does not manage service software installed as packages, during certain upgrade scenarios Cloudera Manager assigns a default CDH version of a cluster. You must manually configure the cluster CDH version to match the package CDH version following the procedure in Configuring the CDH Version for a Cluster in Managing Clusters with Cloudera Manager. If you do not set the cluster CDH version to the package CDH version, Cloudera Manager will incorrectly enable and disable service features based on the configured CDH version.

If your version of Impala was 1.1 or earlier, upgrade to Impala 1.2.1 or later.

When you have finished the upgrade to Cloudera Manager, you can test the installation to verify that the monitoring features are working as expected; follow instructions under Testing the Installation.

Cloudera Manager 5 can manage both CDH 4 and CDH 5, so upgrading existing CDH 4 installations is not required, but you may want to upgrade to the latest version. For more information on upgrading CDH, see Upgrading CDH and Managed Services.