Known Issues in Streams Replication Manager

Known Issues identified in Cloudera Runtime 7.3.1.400 SP2

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.300 SP1 CHF 1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.200 SP1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.100 CHF 1

There are no new known issues identified in this release.

Cloudera Runtime 7.3.1

CDPD-22089: Streams Replication Manager does not sync re-created source topics until the offsets have caught up with target topic: 7.2.17, 7.2.18, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; 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.2.17, 7.2.18, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; 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.2.17, 7.2.18, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; 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.2.17, 7.2.18, 7.3.1, 7.3.1.100, 7.3.1.200, 7.3.1.300, 7.3.1.400; 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.
Streams Replication Manager cannot ensure the exactly-once semantics of transactional source topics: Streams Replication Manager data replication uses at-least-once guarantees, and as a result cannot ensure the exactly-once semantics (EOS) of transactional topics in the backup/target cluster.
note
Even though EOS is not guaranteed, you can still replicate the data of a transactional source, but you must set isolation.level to read_committed for Streams Replication Manager internal consumers. This can be done by adding [***SOURCE CLUSTER ALIAS***]->[***TARGET CLUSTER ALIAS***].consumer.isolation.level=read_committed to the Streams Replication Manager's Replication Configs service property in Cloudera Manager. The isolation.level property can be set on a global connector or replication level. For example:
#Global connector level connectors.consumer.isolation.level=read_committed #Replication level uswest->useast.consumer.isolation.level=read_committed
Streams Replication Manager checkpointing is not supported for transactional source topics: Streams Replication Manager does not correctly translate checkpoints (committed consumer group offsets) for transactional topics. Checkpointing assumes that the offset mapping function is always increasing, but with transactional source topics this is violated. Transactional topics have control messages in them, which take up an offset in the log, but they are never returned on the consumer API. This causes the mappings to decrease, causing issues in the checkpointing feature. As a result of this limitation, failover operations for transactional topics is not possible.