Post-upgrade steps
After successfully upgrading to Cloudera Runtime 7.3.2, ensure that the required post-upgrade steps are also completed.
Reconfigure JVM memory settings after the JDK upgrade
After upgrading to Cloudera Runtime 7.3.2, the JDK version is upgraded to 17. To handle the changed memory requirements introduced by the new JVM version, the upgrade process automatically reconfigures all default JVM memory settings through Cloudera Manager API. This operation updates non-customized memory settings to values appropriate for JDK 17, restarts Cloudera Manager, and restarts all affected services.
Clearing protocol or metadata version in Kafka after upgrading
Clear pinned Kafka Inter-Broker Protocol Version or Kafka Metadata Version on your Cloudera Streams Messaging cluster so Kafka uses the latest protocol or metadata version after upgrade.
When you upgrade to Cloudera Runtime 7.3.2 from an earlier supported version (for example, 7.2.18 or 7.3.1), Cloudera Manager automatically clears these properties as part of the upgrade, starting with Cloudera Runtime 7.3.2.10000 SP1. You do not need this task for that upgrade path.
Service pack upgrades from 7.3.2 to 7.3.2.10000 SP1 do not run that automatic clearing handler. If your cluster was already on 7.3.2 before SP1, verify whether the property is still pinned and use the steps below only if it is.
Complete the following steps only if you are on Cloudera Runtime 7.3.2, you are applying or have applied 7.3.2.10000 SP1, and the property is still set.
