이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 5. Fixed issues
The issues fixed in AMQ Streams 2.1 are shown in the following table. For details of the issues fixed in Kafka 3.1.0, refer to the Kafka 3.1.0 Release Notes.
| Issue Number | Description |
|---|---|
| Cluster operator missing Java options to be passed to Kafka bridge | |
|
Connector gets restarted on every reconciliation when | |
| Errors when scaling-down ZooKeeper nodes | |
| Failure to run on FIPS-enabled clusters | |
| Fix leaking keystores/truststores in ZooKeeperScaler | |
| JVM options provided by the Cluster Operator are ignored | |
| Kafka upgrade, with inter broker protocol and log message format as M.m.p, fails with misleading error | |
| KafkaExporter, CruiseControl and EntityOperator pods are rolled on clients CA renewal | |
| KafkaMirrorMaker2 conditions do not reflect the state of the MM2 connectors | |
| OptimizationFailureException due to invalid CPU utilization | |
| Pass Java system properties to Cruise Control | |
| Rack Awareness doesn’t work for connectors | |
| Set the base image in Kafka Connect Build properly when it is specified in the custom resource | |
| The /tmp volume is not big enough for the compression libraries | |
|
The | |
| The broker is stuck in an inconsistent state after ZooKeeper disconnection | |
| ZooKeeper, Kafka, and EntityOperator certificates are not renewed using your own cluster CA certificate |
| Issue Number | Description |
|---|---|
| CVE-2021-3520 lz4: memory corruption due to an integer overflow bug caused by memmove argument | |
| CVE-2021-43797 netty: control chars in header names may lead to HTTP request smuggling |