Cloudera Docs

Post-upgrade steps

After successfully upgrading to Cloudera Runtime 7.3.2, ensure that the required post-upgrade steps are also completed.

Clearing protocol or metadata version in Kafka after upgrading

After upgrading to Cloudera Runtime 7.3.2, you need to clear the property for the Kafka protocol or metadata versions to ensure that the latest version is used.

Neither rollbacks nor downgrades are possible after you complete the following steps.

  1. Navigate to your Cloudera Streams Messaging Data Hub cluster, and open Cloudera Manager.
  2. In Cloudera Manager, select the Kafka service.
  3. Go to Configuration.
  4. Find and clear the appropriate property for your cluster’s metadata management mode:
    • If your cluster uses ZooKeeper, clear the Kafka Inter‑Broker Protocol Version property.
    • If your cluster uses KRaft, clear the Kafka Metadata Version property.
  5. Save your changes.
  6. Rolling restart the Kafka service.
    1. Select the Kafka service.
    2. Click Actions > Rolling Restart
    3. Ensure that all role types are selected in the Role types to restart list.
    4. Click Rolling Restart.
    5. Click Close once the command has finished.

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.