Cloudera Enterprise 5.15.x | Other versions

Before Upgrading to the Latest Release of CDH

Note:

Before upgrading, read about the latest Incompatible Changes and Known Issues and Workarounds in CDH 5 in the CDH 5 Release Notes.
Warning: Make sure to read Install and Upgrade Known Issues.
If you are upgrading a cluster that is part of a production system, plan ahead. For production clusters, Cloudera recommends allocating up to a full day maintenance window to perform the upgrade, depending on the number of hosts, the amount of experience you have with Hadoop and Linux, and the particular hardware you are using.

The instructions in this section assume you are upgrading a multi-node cluster. If you are running a pseudo-distributed (single-machine) cluster, Cloudera recommends that you copy your data from the cluster, remove the old CDH release, install Hadoop from CDH 5, and then restore your data.

If you have a multi-node cluster running an earlier version of CDH 5, use the appropriate instructions to upgrade your cluster to the latest version:
- Upgrading from CDH 5.4.0 or Higher to the Latest Release
- Upgrading from a Release Lower than CDH 5.4.0 to the Latest Release

Troubleshooting: Upgrading hadoop-kms from 5.2.x and 5.3.x Releases on SLES

This section describes issues that affect SLES upgrades from 5.2.x releases earlier than 5.2.4, and from 5.3.x releases earlier than 5.3.2.

Problem

The problem occurs when you try to upgrade the hadoop-kms package, for example:

Installing: hadoop-kms-2.5.0+cdh5.3.2+801-1.cdh5.3.2.p0.224.sles11 [error]
12:54:19 Installation of hadoop-kms-2.5.0+cdh5.3.2+801-1.cdh5.3.2.p0.224.sles11 failed:
12:54:19 (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: warning: /var/cache/zypp/packages/cdh/RPMS/x86_64/hadoop-kms-2.5.0+cdh5.3.2+801-1.cdh5.3.2.p0.224.sles11.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID e8f86acd
12:54:19 error: %postun(hadoop-kms-2.5.0+cdh5.3.1+791-1.cdh5.3.1.p0.17.sles11.x86_64) scriptlet failed, exit status 1
12:54:19

Note:

The hadoop-kms package is not installed automatically with CDH, so you encounter this error only if you are explicitly upgrading an existing version of KMS.
The examples in this section show an upgrade from CDH 5.3.x; the 5.2.x case looks very similar.

What to Do

If you see an error similar to the one in the example above, proceed as follows:

Abort or ignore the error (either option works):
```
Abort, retry, ignore? [a/r/i] (a): i
```

Perform cleanup:

# rpm -qa hadoop-kms

You will see two versions of hadoop-kms; for example:

hadoop-kms-2.5.0+cdh5.3.1+791-1.cdh5.3.1.p0.17.sles11
hadoop-kms-2.5.0+cdh5.3.2+801-1.cdh5.3.2.p0.224.sles11

Remove the older version, in this example hadoop-kms-2.5.0+cdh5.3.1+791-1.cdh5.3.1.p0.17.sles11:
```
 # rpm -e --noscripts hadoop-kms-2.5.0+cdh5.3.1+791-1.cdh5.3.1.p0.17.sles11
```

Verify that the older version of the package has been removed:
```
# rpm -qa hadoop-kms
```
You should now see only the newer package:
```
hadoop-kms-2.5.0+cdh5.3.2+801-1.cdh5.3.2.p0.224.sles11
```

Page generated May 18, 2018.