Fixed Issues in Kafka

Cloudera Runtime 7.3.2.10000 SP1

OPSAPS-79006: Kafka broker recommission command fails

7.3.2.10000

The Kafka broker Recommission role action failed in Cloudera Runtime 7.3.2 because host IP resolution ran when it was not required for the recommission command. This issue is fixed. You can recommission a previously decommissioned broker after you upgrade to Cloudera Runtime 7.3.2.10000 SP1.

Cloudera Runtime 7.3.2.100 CHF 1

There are no new fixes introduced in this release.

Cloudera Runtime 7.3.2

Cloudera Runtime 7.3.2 resolves Kafka issues and incorporates fixes from the service packs and cumulative hotfixes from 7.3.1.100 through 7.3.1.706. For a comprehensive record of all fixes in Cloudera Runtime 7.3.1.x, see Fixed Issues.

OPSAPS-71679: Ranger resource-based policy creation attempted on each service restart

7.3.2

On each service restart, Kafka, Kafka Connect, and Schema Registry attempted to create Ranger resource-based policies even when the Ranger policy cache was already present. Resource-based policy creation is now skipped when the policy cache file exists, reducing unnecessary Ranger operations on restart.

OPSAPS-75094: Broker rolling restart checks fail on FIPS-enabled clusters with JDK 11 or higher

7.3.2

On FIPS-enabled clusters with JDK 11 or higher, CSD_JAVA_OPTS was not propagated to the Kafka broker rolling restart check scripts, which caused the checks to fail. The rolling restart check scripts now receive the CSD_JAVA_OPTS value on FIPS-enabled clusters.

DBZ-4990: The Debezium Db2 Source connector does not support schema evolution

7.3.2

This issue is fixed. For more information, see DBZ-4990.

None.

OPSAPS-69317: Kafka Connect Rolling Restart Check fails if SSL Client authentication is required

7.3.2

Rolling restart checks for Kafka Connect failed when mutual TLS was required (ssl.client.auth set to required), even though the service was healthy. This issue is fixed.