Step 3: Upgrading the Cloudera Manager Server
Loading Filters ... 5.16 5.15 5.14 5.13 7.6.7 7.4.4 5.16 5.15 5.14 5.13 7.1.7.2000 7.1.7
You can also use the procedures on this page to install Cloudera Manager patches. You must obtain the download URL for the patch before proceeding – you will use this information later in this procedure.
This topic provides procedures for backing up the Cloudera Manager Server.
Minimum Required Role: Cluster Administrator (also provided by Full Administrator)
After you complete the steps in Step 1: Getting Started Upgrading Cloudera Manager 5 and Step 2: Backing Up Cloudera Manager 5, continue with the following:
Establish Access to the Software
Cloudera Manager needs access to a package repository that contains the updated software packages. You can choose to access the Cloudera public repositories directly, or you can download those repositories and set up a local repository to access them from within your network. If your cluster hosts do not have connectivity to the Internet, you must set up a local repository.
If you have enabled high availability for Cloudera Manager, perform the following steps on the hosts for both the active and passive instances of the Cloudera Manager server.
- Log in to the Cloudera Manager Server host.
ssh my_cloudera_manager_server_host
- Remove any older files in the existing
repository directory:
- RHEL / CentOS
-
sudo rm /etc/yum.repos.d/cloudera*manager.repo*
- SLES
-
sudo rm /etc/zypp/repos.d/cloudera*manager.repo*
- Ubuntu
-
sudo rm /etc/apt/sources.list.d/cloudera*.list*
- Fill in the form at the top of this page.
- Create a repository file so that the package
manager can locate and download the binaries.
Do one of the following, depending on whether or not you are using a local package repository:
-
Use a local package repository. (Required when cluster hosts do not have access to the internet.) See Configuring a Local Package epository.
-
Use the Cloudera public repository
- RHEL / CentOS
-
- Create a file named
/etc/yum.repos.d/cloudera-manager.repo
with the following content:[cloudera-manager] name=Cloudera Manager baseurl=https://archive.cloudera.com/p/cm7/<Cloudera Manager version>/redhat<OS major version>/yum/ gpgkey =https://archive.cloudera.com/p/cm7/<Cloudera Manager version>/redhat<OS major version>/yum/RPM-GPG-KEY-cloudera username=changeme password=changeme gpgcheck=1 enabled=1 autorefresh=0 type=rpm-md
Replace
changeme
with yourusername
andpassword
in the/etc/yum.repos.d/cloudera-manager.repo
file.
- Create a file named
- SLES
-
- Create a file named
/etc/zypp/repos.d/cloudera-manager.repo
with the following content:[cloudera-manager] name=Cloudera Manager baseurl=https://archive.cloudera.com/p/cm7/<Cloudera Manager version>/sles<OS major version>/yum/ gpgkey =https://archive.cloudera.com/p/cm7/<Cloudera Manager version>/sles<OS major version>/yum/RPM-GPG-KEY-cloudera username=changeme password=changeme gpgcheck=1 enabled=1 autorefresh=0 type=rpm-md
-
Replace
changeme
with yourusername
andpassword
in the/etc/zypp/repos.d/cloudera-manager.repo
file.
- Create a file named
- Ubuntu
-
Debian is not a supported operating system for Cloudera Manager 6.x.
- Create a file named
/etc/apt/sources.list.d/cloudera_manager.list
with the following content:# Cloudera Manager <Cloudera Manager version> deb [arch=amd64] http://username:password@archive.cloudera.com/p/cm7/<Cloudera Manager version>/ubuntu1804/apt -cm<Cloudera Manager version> contrib
- Run the following
command:
sudo apt-get update
-
Replace
changeme
with yourusername
andpassword
in the/etc/apt/sources.list.d/cloudera_manager.list
file.
- Create a file named
-
- A Cloudera Manager upgrade can introduce
new package dependencies. Your organization may have restrictions or
require prior approval for installation of new packages. You can
determine which packages may be installed or upgraded:
- RHEL / CentOS
-
yum deplist cloudera-manager-agent
- SLES
-
zypper info --requires cloudera-manager-agent
- Ubuntu
-
apt-cache depends cloudera-manager-agent
Install Java (JDK)
Oracle JDK 1.8 is required on all cluster hosts managed by Cloudera Manager 6.0.0 or higher. If it is supported for your version of Cloudera Manager, you can also install OpenJDK 8*, OpenJDK 11*, or OpenJDK 17*. See Manually Installing OpenJDK. If OpenJDK 8* is already installed on your hosts, skip the steps in this section.
If you are upgrading to Cloudera Manager 6.0.0 or higher, you can manually install JDK 8 on the Cloudera Manager server host, and then, as part of the Cloudera Manager upgrade process, you can specify that Cloudera Manager upgrade the JDK on the remaining hosts.
- Log in to the Cloudera Manager Server host.
ssh my_cloudera_manager_server_host
- Stop the Cloudera Manager
Server.
sudo systemctl stop cloudera-scm-server
- Remove the JDK:
- Perform the following steps on all hosts managed by Cloudera Manager:
- Run the following command to remove the JDK, using the package names from
Step 1: (If you do
not delete these files, Cloudera Manager and other components may continue to use the
old version of the JDK.)
- RHEL
-
yum remove <JDK package name>
- Ubuntu
-
apt-get remove <JDK package name>
- SLES
-
zypper rm <JDK package name>
- Confirm that the package has been removed:
- RHEL
-
yum list installed |grep -i java
- Ubuntu
-
apt list --installed | grep -i java
- SLES
-
zypper search --installed-only |grep -i java
- Run the following command to remove the JDK, using the package names from
Step 1: (If you do
not delete these files, Cloudera Manager and other components may continue to use the
old version of the JDK.)
- Perform the following steps on all hosts managed by Cloudera Manager:
- Install OpenJDK
- Start the Cloudera Manager
Server.
sudo systemctl start cloudera-scm-server
Upgrade the Cloudera Manager Server
- Log in to the Cloudera Manager server host.
- Stop the Cloudera Management Service.
- Log in to the Cloudera Manager Admin Console.
- Select .
- Select .
- Ensure that you have disabled any scheduled replication or snapshot jobs and wait for any running commands from the Cloudera Manager Admin Console to complete before proceeding with the upgrade.
- If you have any Hive Replication Schedules that replicate to a cloud destination, delete these replication clusters before continuing with the upgrade. You can re-create these Replication Schedules after the Cloudera Manager upgrade is complete.
- If your cluster is running Ubuntu version 18, stop all clusters before upgrading Cloudera Manager. (For each cluster, go to .)
- Stop the Cloudera Manager server host, agent, and embedded database
(if installed). If you have enabled high availability for Cloudera
Manager, perform the following steps on the hosts for both the
active and passive instances of Cloudera Manager:
- Log in to the Cloudera Manager Server
host:
ssh my_cloudera_manager_server_host
- Stop the Cloudera Manager
Server.
sudo systemctl stop cloudera-scm-server
- Stop the Cloudera Manager Agent.
- RHEL 7, SLES 12, Ubuntu 18.04 and higher
-
sudo systemctl stop cloudera-scm-agent
- RHEL 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04 or 14.04
-
sudo service cloudera-scm-agent stop
- Log in to the Cloudera Manager Server
host:
- Upgrade the Cloudera Manager software. If you have enabled high
availability for Cloudera Manager, perform the following steps on the
hosts for both the active and passive instances of the Cloudera
Manager server.
- Upgrade the packages.
- RHEL / CentOS
-
sudo yum clean all sudo yum upgrade cloudera-manager-server cloudera-manager-daemons cloudera-manager-agent
cloudera-manager-server-db-2
- SLES
-
sudo zypper clean --all sudo zypper up cloudera-manager-server cloudera-manager-daemons cloudera-manager-agent
cloudera-manager-server-db-2
- Ubuntu
-
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
cloudera-manager-server-db-2
You might 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 may receive a similar prompt for
/etc/cloudera-scm-server/db.properties
. Answer N to both prompts.You may be prompted to accept the GPG key. Answer y.
Retrieving key from https://archive.cloudera.com/.../cm/RPM-GPG-KEY-cloudera Importing GPG key ... Userid : "Yum Maintainer <webmaster@cloudera.com>" Fingerprint: ... From : https://archive.cloudera.com/.../RPM-GPG-KEY-cloudera
- If you customized the
/etc/cloudera-scm-agent/config.ini
file, your customized file is renamed with the extension.rpmsave
or.dpkg-old
. Merge any customizations into the/etc/cloudera-scm-agent/config.ini
file that is installed by the package manager. -
Verify that you have the correct packages installed.
- Ubuntu
-
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.15.0-0.cm...~sq The Cloudera Manager Agent ii cloudera-manager-daemo 5.15.0-0.cm...~sq Provides daemons for monitoring Hadoop and related tools. ii cloudera-manager-serve 5.15.0-0.cm...~sq The Cloudera Manager Server
- RHEL / CentOS / SLES
-
rpm -qa 'cloudera-manager-*'
cloudera-manager-server-5.15.0-... cloudera-manager-agent-5.15.0-... cloudera-manager-daemons-5.15.0-...
cloudera-manager-server-db-2-5.15.0-...
- Upgrade the packages.
- Start the Cloudera Manager agent and server. If you have enabled
high availability for Cloudera Manager, start only the host for the
active instance of Cloudera Manager:
- Start the Cloudera Manager Agent.
- RHEL 7, SLES 12, Ubuntu 18.04 and higher
-
If the agent starts without errors, no response displays.sudo systemctl start cloudera-scm-agent
- RHEL 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04 or 14.04
-
You should see the following:sudo service cloudera-scm-agent start
Starting cloudera-scm-agent: [ OK ]
- The
Cloudera Manager server now requires 4GB of heap. On the Cloudera
Manager server host, edit the
/etc/default/cloudera-scm-server
file and change the line that begins withexport CMF_JAVA_OPTS=
. Change the-Xmx2G
parameter to-Xmx4G
. - Start the Cloudera Manager
Server.
sudo systemctl start cloudera-scm-server
- If you have problems starting the server or the agent, such as
database permissions problems, you can use log files to
troubleshoot the problem:
Server log:
tail -f /var/log/cloudera-scm-server/cloudera-scm-server.log
Agent log:
ortail -f /var/log/cloudera-scm-agent/cloudera-scm-agent.log
tail -f /var/log/messages
- Start the Cloudera Manager Agent.
- Verify that all cluster hosts appear in the Cloudera Manager Admin
Console.
- Use a Web browser to open the Cloudera Manager Admin Console
using the following
URL:
It can take several minutes for the Cloudera Manager Server to start, and the Cloudera Manager Admin Console is unavailable until the server startup is complete and the Upgrade Cloudera Manager page displays.http://cloudera_Manager_server_hostname:7180/cmf/upgrade
- Verify that all cluster hosts are visible. (Go to .)
- Use a Web browser to open the Cloudera Manager Admin Console
using the following
URL:
- If you have enabled high availability for Cloudera Manager, start
the host for the passive instance of Cloudera Manager:
- Start the Cloudera Manager Agent.
- RHEL 7, SLES 12, Ubuntu 18.04 and higher
-
If the agent starts without errors, no response displays.sudo systemctl start cloudera-scm-agent
- RHEL 5 or 6, SLES 11, Debian 6 or 7, Ubuntu 12.04 or 14.04
-
You should see the following:sudo service cloudera-scm-agent start
Starting cloudera-scm-agent: [ OK ]
- The
Cloudera Manager server now requires 4GB of heap. On the Cloudera
Manager server host, edit the
/etc/default/cloudera-scm-server
file and change the line that begins withexport CMF_JAVA_OPTS=
. Change the-Xmx2G
parameter to-Xmx4G
. - Start the Cloudera Manager
Server.
sudo systemctl start cloudera-scm-server
- If you have problems starting the server or the agent, such as
database permissions problems, you can use log files to
troubleshoot the problem:
Server log:
tail -f /var/log/cloudera-scm-server/cloudera-scm-server.log
Agent log:
ortail -f /var/log/cloudera-scm-agent/cloudera-scm-agent.log
tail -f /var/log/messages
- Start the Cloudera Manager Agent.
To complete the Cloudera Manager upgrade, continue with Step 4: Upgrading the Cloudera Manager Agents.