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

      For example, for Red Hat or CentOS 6, you would go to https://archive.cloudera.com/cm5/redhat/6/x86_64/cm/. In that directory, find the repo file that contains information including the repository base URL and GPG key. The contents of the cloudera-manager.repo are similar to the following:

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

      For Ubuntu or Debian systems, go to the appropriate release directory, for example, https://archive.cloudera.com/cm4/debian/wheezy/amd64/cm. The repo file, in this case, cloudera.list, is similar to the following:

      # Packages for Cloudera Manager, Version 5, on Debian 7.0 x86_64
      deb https://archive.cloudera.com/cm5/debian/wheezy/amd64/cm wheezy-cm5 contrib
      deb-src https://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-manager-server cloudera-manager-daemons cloudera-manager-agent   Note: yum clean all cleans yum cache directories, ensuring that you download and install the latest versions of the packages. If your system is not up to date, any underlying system components must be upgraded before yum update can succeed. yum indicates which components must be upgraded. If the Cloudera Manager instance you are upgrading uses the embedded PostgreSQL database, add cloudera-manager-server-db-2 to the list of packages in the yum upgrade command. The embedded PostgreSQL database should not be used in production environments.
      SLES	$ sudo zypper clean --all $ sudo zypper up -r https://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	The following commands 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-daemons cloudera-manager-agent If the Cloudera Manager instance you are upgrading uses the embedded PostgreSQL database, add cloudera-manager-server-db-2 to the list of packages in the apt-get install command. The embedded PostgreSQL database should not be used in production environments. During this process, you may be prompted about 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 prompts.

2. If you customized /etc/cloudera-scm-agent/config.ini, your customized file is moved to a file with the extension .rpmsave or .dpkg-old. Merge any customizations into /etc/cloudera-scm-agent/config.ini installed by the package manager.

$ rpm -qa 'cloudera-manager-*'
cloudera-manager-repository-5.0-1.noarch
cloudera-manager-server-5.8.0-0.cm580.p0.41.el6.x86_64
cloudera-manager-agent-5.8.0-0.cm580.p0.41.el6.x86_64
cloudera-manager-daemons-5.8.0-0.cm580.p0.41.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.8.0-0.cm580.p0.41~sq The Cloudera Manager Agent
ii  cloudera-manager-daemo 5.8.0-0.cm580.p0.41~sq Provides daemons for monitoring Hadoop and related tools.
ii  cloudera-manager-serve 5.8.0-0.cm580.p0.41~sq The Cloudera Manager Server

$ sudo mkdir /opt/cloudera-manager

$ sudo tar xzf cloudera-manager*.tar.gz -C /opt/cloudera-manager

The files are extracted to a subdirectory named according to the Cloudera Manager version being extracted. For example, files could be extracted to /opt/cloudera-manager/cm-5.0/. This full path is needed later and is referred to as tarball_root directory.

$ sudo useradd --system --home=/opt/cloudera-manager/cm-5.6.0/run/cloudera-scm-server --no-create-home --shell=/bin/false --comment "Cloudera SCM User" cloudera-scm

If the Cloudera Manager Server does not start, see Troubleshooting Installation and Upgrade Problems.

  Important: All hosts in the cluster must have access to the Internet if you 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 is the Matched Release for this Cloudera Manager Server. However, if you used a custom repository (instead of 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.
     3. Click Continue. The JDK Installation Options page displays.
        • Leave Install Oracle Java SE Development Kit (JDK) checked to allow Cloudera Manager to install the JDK on each cluster host, or uncheck if you plan to install it yourself.
        • If local laws permit you to deploy unlimited strength encryption, and you are running a secure cluster, check the Install Java Unlimited Strength Encryption Policy Files checkbox.
        Click Continue.
     4. Specify credentials and initiate Agent installation:
        • Select root or enter the username for an account that has password-less sudo permission.
        • Select an authentication method:
          • If you choose password authentication, enter and confirm the password.
          • If you choose public-key authentication, provide a passphrase and path to the required key files.
        • You can specify an alternate SSH port. The default value is 22.
        • 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.
     6. 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 rerun the inspector. When you are satisfied with the inspection results, click Finish.
   • Manually install Agent software
     1. On all cluster hosts except the Cloudera Manager Server host, stop the Agent:

        $ sudo service cloudera-scm-agent stop

     2. In the Cloudera Admin Console, select No, I would like to skip the agent upgrade now and click Continue.
     3. Copy the appropriate repo file as described in Upgrade Cloudera Manager Server (Packages).
     4. Run the following commands:

        Operating System	Commands
        RHEL	$ sudo yum clean all $ sudo yum upgrade cloudera-manager-server cloudera-manager-daemons cloudera-manager-agent   Note: yum clean all cleans yum cache directories, ensuring that you download and install the latest versions of the packages. If your system is not up to date, any underlying system components must be upgraded before yum update can succeed. yum indicates which components must be upgraded. If the Cloudera Manager instance you are upgrading uses the embedded PostgreSQL database, add cloudera-manager-server-db-2 to the list of packages in the yum upgrade command. The embedded PostgreSQL database should not be used in production environments.
        SLES	$ sudo zypper clean --all $ sudo zypper up -r https://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 During this process, you may be prompted about 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 prompts.

     5. If you customized /etc/cloudera-scm-agent/config.ini, your customized file is moved to a file with the extension .rpmsave or .dpkg-old. Merge any customizations into /etc/cloudera-scm-agent/config.ini installed by the package manager.
     6. On all cluster hosts, start the Agent:

        $ sudo service cloudera-scm-agent start

3. If you are upgrading from a free version of Cloudera Manager prior to 4.6:
   1. Click Continue to assign the Cloudera Management Services roles to hosts.
   2. If you are upgrading to Cloudera Enterprise, specify required databases:
      1. Choose the database type:
         • Keep the default setting of Use Embedded Database to have Cloudera Manager create and configure required databases. Record the auto-generated passwords.
           
           
         • Select Use Custom Databases to specify external database host, enter the database type, database name, username, and password for the database that you created when you set up the database.
         • If you are adding the Oozie service, you can change your Oozie configuration to control when data is purged to improve performance, cut down on database disk usage, improve upgrade performance, or to keep the history for a longer period of time. See Configuring Oozie Data Purge Settings Using Cloudera Manager.
      2. Click Test Connection to confirm that Cloudera Manager can communicate with the database 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 database and then try the test again. (For some servers, if you are using the embedded database, you will see a message saying the database will be created at a later step in the installation process.)

         The Cluster Setup Review Changes screen displays.

4. Click Finish.
5. 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, the newly created Hive Metastore Server also uses Derby. Because Derby does not allow concurrent connections, Hue continues to work, but the new Hive Metastore Server does not 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 and recommends 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 and higher. This ensures that the upgrade does not disrupt your existing setup. You should plan to disable the bypass mode, especially when using CDH 4.2 and higher. 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 redeploy 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.
6. If you are upgrading from Cloudera Manager 4.5 and lower, correct the Hive home directory permissions (/user/hive) as follows:

   sudo -u hdfs hdfs dfs -chown hive:hive /user/hive/
   sudo -u hdfs hdfs dfs -chmod 1775 /user/hive/

7. If you are upgrading from Cloudera Manager prior to 4.8 and have an Impala service, assign the Impala Catalog Server role to a host.
8. Review the configuration changes to be applied.
9. Click Finish.

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