Cloudera Manager 5 Upgrade (official translation collation, enterprise-class combat validation) __CDH

This document is suitable for all versions of Cloudera Manager 5 and is upgraded using Tarballs tarballs contains Cloudera Manager server and Cloudera manageragent.

Https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_ug_cm5_tarballs.html#cm_ag_ug_cm5_tarballs

In most scenarios, upgrading Cloudera Manager is probably not required to turn off large data CDH services, just to stop some dependent services. CDH Daemons continues to run and is unaffected. Cloudera Manager also does not affect the installation of CDH.

To upgrade Cloudera Manager 5 using tarballs:

Steps	Describe	Link
1	Gather information about the need to upgrade Cloudera manager, including user accounts, passwords, database URLs, and other information. You must collect this information from the very beginning of the upgrade, because some information can only be obtained from the Cloudera Manager Admin console, and will not be accessible if you collect it during the upgrade.	Step 1:collect Upgrade Information
2	Complete the steps before the upgrade and review some special warnings in the upgrade	Step 2:complete pre-upgrade Steps
3	If your Cloudera Manager host uses an unsupported JDK version, you must upgrade the supported JDK version prior to upgrading Cloudera Manager. If you plan to upgrade CDH, you must also upgrade the JDK at all cluster nodes.	Step 3:upgrade The JDK Upgrading to Oracle JDK 1.7 Upgrading to Oracle JDK 1.8
4	If the Cloudera Manager node is unable to access the extranet, or if you install a lower-than-current version of Cloudera Manager, you need to configure the Cloudera public access to the Cloudera Manager software package Repository or a local package repository.	Step 4:creating and Using a Package Repository for Cloudera Manager http://archive.cloudera.com/cm5/repo-as-tarball/5.8.4/
5	Upgrade Cloudera Navigator Data Management components if you upgrade from Cloudera Navigator 2.6 or lower.	Step 5:upgrading the Cloudera Navigator Data Management Component
6	Upgrade Cloudera Manager Server and Agent software	Step 6:upgrading the Cloudera Manager Server and Agents
7	Verifying and testing the upgrade results	Step 7:verify and Test the Upgrade
8	Upgrade any components that require Cloudera Navigator: Cloudera Manager Key Trustee Server Cloudera Navigator Key HSM Cloudera Navigator Key Trustee KMS Cloudera Navigator Encrypt When you upgrade Cloudera Manager, these Cloudera Navigator Data Management Componen will be upgraded.	Step 8:upgrading Cloudera Navigator components
9	(optional) Upgrade CDH. If you do not need to upgrade CDH immediately after the Cloudera manager upgrade, you can also consider upgrading CDH later.	Step 9: (Optional) Upgrade CDH

Step 1: Gather upgrade information

Before you upgrade Cloudera Manager, gather the following information:

1. Host Credentials

Root or a user with sudo permissions

2. Cloudera Manager Cluster version information

Support > About

3. JDK version in cluster

Support > About

4. CDH version

The CDH version number displays next to Thecluster name on the home page.

5. Cluster installation mode, parcels or packages

This is information displays next to the Cdhversion on the home page of Cloudera Manager.

6. Cluster-enabled services

Clusters > Cluster name.

7. Type and version of the operating system

Go to the Hosts and click on a hostname in thelist. The operating system type and version displays in the Distribution row inthe Details section.

Step 2: Complete the pre-upgrade step

Before you start Cloudera Manager upgrade, deal with things:

1. Check the content of the Web site below for your upgrade to the new version of the environment.

Https://www.cloudera.com/documentation/enterprise/release-notes/topics/rn_consolidated_pcm.html

2. Read Cloudera Manager 5 release Notes

Https://www.cloudera.com/documentation/enterprise/release-notes/topics/rg_release_notes_cm.html

3. Read Cloudera Security Bulletins

Https://www.cloudera.com/documentation/other/security-bulletins/topics/Security-Bulletin.html

4. Note the following note:

L Cloudera Management Service TLS/SSL Configuration

If you turn on TLS security control for the Cloudera Manager Admin console, because the Clouderamanager 5.1 version, Cloudera service roles uses TLS and Cloudera manager interaction and fails to start until the Tls/ssl property is configured.

L Navigator

If you open the Clouderanavigator auditing, auditing will block during the Cloudera Manager 5 upgrade, and it will only be restarted when you restart the auditing service role. You will be instructed to stop some of the services in subsequent steps.

5. If you have previously installed Kafka 1.2 and upgraded from Cloudera Manager 5.4 or lower, remove Kafka CSD:

A. Determining the location of the CSD catalogue

(1) Choose Administration > Settings

(2) Click Custom Service Descriptors Directory

(3) Re-retrieve the directory from the local descriptor Repository Path Property

B. Removing the Kafka CSD from the directory

6. Review use RPM to install the dependencies. Clouderamanager upgrades may introduce new package dependencies.

Https://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_package_dependencies.html#package_dependencies

Step 3: Upgrade JDK

Upgrade to JDK 1.7:

https://www.cloudera.com/documentation/enterprise/latest/topics/cdh_cm_upgrading_to_jdk7.html#concept_j2f_5gh_4r

Upgrade to JDK 1.8:

Https://www.cloudera.com/documentation/enterprise/latest/topics/cdh_cm_upgrading_to_jdk8.html#xd_ 583c10bfdbd326ba-590cb1d1-149e9ca9886--7c46

Step 4: For Cloudera Manager, create and use package Repository

Create a fixed repo

1. Install Apache HTTPD

Yum Install httpd

Service httpd Start

2. Download Tarball

http://archive.cloudera.com/cm5/repo-as-tarball/?_ga=1.64295087.1254641687.1490056758

For the Cloudera Navigator Data encryption component, enter each component for download:

· Cloudera Navigator Key Trustee Server

· Cloudera Navigator Key HSM

· Cloudera Navigator Key Trustee KMS

· Cloudera Navigator Encrypt

3. Decompression cm installation package, and copy to the Web server directory, modify permissions

Tar Xvfz cm5.8.4-centos7.tar.gz

MV Cm/var/www/html

Chmod-r ugo+rx/var/www/html/cm

Create a temporary repo

>> Download Tarball

http://archive.cloudera.com/cm5/repo-as-tarball/?_ga=1.64295087.1254641687.1490056758

For the Cloudera Navigator Data encryption component, enter each component for download:

· Cloudera Navigator Key Trustee Server

· Cloudera Navigator Key HSM

· Cloudera Navigator Key Trustee KMS

· Cloudera Navigator Encrypt

>> Decompression cm installation package, modify permissions

Tar Xvfz cm5.8.4-centos7.tar.gz

Chmod-r ugo+rx/tmp/cm

>> Start Simplehttpserver

cd/tmp/cm

Python-m Simplehttpserver 8900

Step 5: Upgrade Cloudera Navigator Data Management Component

If you upgrade from Cloudera Navigator 2.6 or lower, upgrade Cloudera Navigator Data Management Component.

Https://www.cloudera.com/documentation/enterprise/latest/topics/cn_iu_upgrade_navigator.html

Step 6: Upgrade Cloudera Manager Server and agents

1. If your cluster uses an embedded PostgreSQL database, stop all services that use the PG database, including:

Hive service and the use of Hive Metastore services, such as Impala,hue, etc.

Oozie

Sentry

2. Stop Cloudera Managerserver and Agent

A. Use the Cloudera manageradmin console to stop a running command, or wait for the command to finish

Primary: If you do not stop all commands, the start of Cloudera Manager server will fail after the upgrade is complete.

B. Cloudera Managerserver to stop running

Service Cloudera-scm-server Stop

C. If you use an embedded PostgreSQL database, stop the database

Servicecloudera-scm-server-db stop

D. If the Cloudera Manager node is running the Clouderamanager Agent, you need to stop

Service Cloudera-scm-agent Stop

3. Download Tarballs

4. Copy the downloaded tarballs to all Cloudera Manager server and agent, and unzip

Mkdir/opt/cloudera-manager

Tar xzf Cloudera-manager*.tar.gz-c/opt/cloudera-manager

5. At each Cloudera agent node, configure the Cloudera Manager agent to point to Cloudera manager Server

Tarball_root/etc/cloudera-scm-agent/config.ini

Property	Description
Server_host	Name of the host where Cloudera Manager Server is running.
Server_port	Port on the host where Cloudera Manager Server is running.

6. By default, for Tarball installations, there is a VAR subdirectory for saving state information. For tarball deployments, the state is saved by default in the operating system's/var directory.