Known issues and technical limitations for Streams Replication Manager are
addressed in Cloudera Runtime 7.3.3.
Known issues identified in Cloudera Runtime 7.3.3
There are no new known issues identified in this release.
Known issues identified before Cloudera Runtime 7.3.3
Known issues identified before Cloudera Runtime 7.3.3 include only
unresolved issues from previous releases that continue to affect the Cloudera Runtime 7.3.3 release.
- CDPD-105439: Streams Replication Manager becomes unavailable when Kafka crashes due to
PAM authentication on RHEL 9 or Rocky Linux 9
- 7.1.9, 7.2.18, 7.3.1, 7.3.2
- On RHEL 9 or Rocky Linux 9 versions 9.1 through 9.7, a
concurrency bug in
libeconf 0.4.1 causes libpam to
crash under high concurrent load. This affects Kafka when configured to use PAM authentication. When handling
multiple concurrent requests, libpam could crash, causing the Kafka JVM
to crash. Because Streams Replication Manager depends on Kafka, SRM also becomes unavailable
after some time.
- Use AD/LDAP authentication instead of PAM authentication.
- Upgrade the OS to RHEL 9.8 or Rocky Linux 9.8.
- Update
libeconf to libeconf-0.4.1-7.el9_8 by
running dnf update libeconf.
- CDPD-22089: Streams Replication Manager does not sync
re-created source topics until the offsets have caught up with target topic
- 7.1.7 and all its SP and CHF releases, 7.1.9 and all its SP and CHF releases, 7.3.1 and all its SP and CHF releases, 7.3.2
- Messages written to topics that were deleted and re-created are
not replicated until the source topic reaches the same offset as the target topic. For
example, if at the time of deletion and re-creation there are a 100 messages on the
source and target clusters, new messages will only get replicated once the re-created
source topic has 100 messages. This leads to messages being lost.
- None
- CDPD-11079: Blacklisted topics appear in the list of replicated
topics
- 7.1.7 and all its SP and CHF releases, 7.1.9 and all its SP and CHF releases, 7.3.1 and all its SP and CHF releases, 7.3.2
- If a topic was originally replicated but was later disallowed
(blacklisted), it will still appear as a replicated topic under the
/remote-topics REST API endpoint. As a result, if a call is made to
this endpoint, the disallowed topic will be included in the response. Additionally, the
disallowed topic will also be visible in the Streams Messaging Manager UI.
However, it's Partitions and Consumer Groups will be 0, its Throughput, Replication
Latency and Checkpoint Latency will show N/A.
- None
- CDPD-30275: Streams Replication Manager may
automatically re-create deleted topics on target clusters
- 7.1.9 and all its SP and CHF releases, 7.3.1 and all its SP and CHF releases, 7.3.2
- If
auto.create.topics.enable is enabled,
deleted topics might get automatically re-created on target clusters. This is a timing
issue. It only occurs if remote topics are deleted while the replication of the topic is
still ongoing.
-
- Remove the topic from the topic allowlist with
srm-control. For
example:srm-control topics --source [SOURCE_CLUSTER] --target [TARGET_CLUSTER] --remove [TOPIC1]
- Wait until Streams Replication Manager is no longer replicating the
topic.
- Delete the remote topic in the target cluster.
- CDPD-80872: Streams Replication Manager replication-records-lag is incorrect
on empty partitions with non-zero end offset
- 7.1.9 and all its SP and CHF releases, 7.3.1 and all its SP and CHF releases, 7.3.2
- When a replicated partition is empty and its end offset is
non-zero, the
replication-records-lag metric is incorrectly reported as
the end offset (instead of 0 or NaN).
- Wait for a new message to be written into the partition.
When it gets replicated, the metric is reported correctly.
Limitations
- Streams Replication Manager cannot replicate Ranger
authorization policies to or from Kafka clusters
- Due to a limitation in the Kafka-Ranger plugin, Streams Replication Manager cannot replicate Ranger policies to or from clusters
that are configured to use Ranger for authorization. If you are using Streams Replication Manager to replicate data to or from a cluster that uses
Ranger, disable authorization policy synchronization in Streams Replication Manager. This can be achieved by clearing the
Sync Topic Acls Enabled
(
sync.topic.acls.enabled) checkbox.