Step 2: Review Notes and Warnings

Notes and warnings to consider before upgrading to CDP.

Loading Filters ... 7.0.3 7.1.1 7.1.2 7.1.3 7.1.4 7.2.4 7.3.1 7.4.4 7.5.1 7.6.1 7.6.7 7.7.1 7.7.3 7.11.3 7.1.7.2000 7.1.8 7.1.7.1000 7.1.7 7.1.6 7.1.5 7.1.4 7.1.3 7.1.2 7.1.1 7.1.9

Minimum Required Role: Cluster Administrator (also provided by Full Administrator) This feature is not available when using Cloudera Manager to manage Data Hub clusters.

Note the following before upgrading your clusters:

Cruise Control might fail during an upgrade

Cruise Control does not function properly during the upgrade

Data replication with Streams Replication Manager might stop during a rolling upgrade

Prometheus instances used by Streams Messaging Manager require reconfiguration following an upgrade

The integration between Streams Messaging Manager and Streams Replication Manager is changed

HDFS

Ozone notes

Known issue during 7.1.7 SP2 to 7.1.9 upgrade

OPSAPS-68279: When upgrading CDp 7.1.7 SP2 to CDP 719, sometimes the command step DeployClientConfig fails due to the following error:
Error Message:Client configuration generation requires the following additional parcels to be activated:[cdh]
This can be because of the failure of the activation of the 7.1.9 parcels. To verify:
  1. Navigate to the parcels page.
  2. See if the following error is displayed: Error when distributing to <hostname>: Sc file/opt/cloudera/parcels/.flood/CDH-7.1.9-1.cdh7.1.9.p0.43968053-el7.parcel/CDH-7.1. 1.cdh7.1.9.0.43968053-el7.parcel does not exist.
  3. Using the error above, identify the host and ssh into the host by running the command ssh <hostname>.
  4. Navigate to the agent directory by running the command cd /var/log/cloudera-scm-agent.
  5. Find the following pattern in agent log file(s) Exception: Untar failed with return code: 2, with tar output: stdout: [b''], stderr: [b'\ngzip: stdin: invalid compressed data--format violated\ntar: Unexpected EOF in archive\ntar: Unexpected EOF in archive\ntar: Error is not recoverable: exiting now\n'].
  1. If the above exception appears, you must restart the agent on that host by running the command systemctl restart cloudera-scm-agent.
  2. After the agent restarts, click resume to continue with the upgrade.