Known Issues in Streams Replication Manager

Learn about the known issues in Streams Replication Manager, the impact or changes to the functionality, and the workaround.

Known Issues

CDPD-22089: SRM does not sync re-created source topics until the offsets have caught up with target topic
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.
CDPD-14019: SRM may automatically re-create deleted topics
If auto.create.topics.enable is enabled, deleted topics are automatically recreated on source clusters.
Prior to deletion, remove the topic from the topic allowlist with the srm-control tool. This prevents topics from being re-created.
srm-control topics --source [SOURCE_CLUSTER] --target [TARGET_CLUSTER] --remove [TOPIC1][TOPIC2]
CDPD-11079: Blacklisted topics appear in the list of replicated topics
If a topic was originally replicated but was later excluded for replication, 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, this topic will be included in the response. Additionally, the excluded topic will also be visible in the SMM UI. However, it's Partitions and Consumer Groups will be 0, its Throughput, Replication Latency and Checkpoint Latency will show N/A.
CDPD-60823: Configuring the SRM Client's secure storage is mandatory for unsecured environments
In an unsecured environment the srm-control tool should not need any additional configuration to run. However, due to an issue with the automatic generation of the default configuration, configuring the SRM Client's secure storage is mandatory for the srm-control tool. This is true even if none of the clusters that the tool connects to are secured.
If a secure storage is not configured, the tool will fail with the following NullPointerException:
at com.cloudera.dim.mirror.SecureConfigProvider.retrievePassword(
at com.cloudera.dim.mirror.SecureConfigProvider.configure(
at org.apache.kafka.common.config.AbstractConfig.instantiateConfigProviders(
at org.apache.kafka.common.config.AbstractConfig.resolveConfigVariables(
at org.apache.kafka.common.config.AbstractConfig.<init>(
at org.apache.kafka.common.config.AbstractConfig.<init>(
at org.apache.kafka.connect.mirror.MirrorMakerConfig.<init>(
at com.cloudera.dim.mirror.MirrorControlCommand$SourceTargetCommand.init(
at com.cloudera.dim.mirror.MirrorControlCommand.issueCommand(
at com.cloudera.dim.mirror.MirrorControlCommand.main(
Configure a secure storage password and set it as an environment variable in your CLI session before running the srm-control tool.
  1. In Cloudera Manager, select the Streams Replication Manager service.
  2. Go to Configuration.
  3. Find and configure the SRM Client's Secure Storage Password property.

    Take note of the password that you configure.

  4. Click Save changes.

  5. Restart the SRM service
  6. SSH into one of the SRM hosts in your cluster.
  7. Set the secure storage password as an environment variable.
    Replace [***SECURE STORAGE ENV VAR***] with the name of the environment variable you specified in Environment Variable Holding SRM Client's Secure Storage Password. Replace [***SRM SECURE STORAGE PASSWORD***] with the password you specified in SRM Client's Secure Storage Password. For example:
    export SECURESTOREPASS=”mypassword”
OPSAPS-61001: Saving configuration changes for SRM is not possible
Cloudera Manager incorrectly labels the SRM Client's Secure Storage Password property as mandatory. Moreover, it does not offer this property for configuration when SRM is installed with the Add Service Wizard.

As a result, it is possible to install and start SRM without configuring this property. However, in a case like this, making changes to SRM's configuration is not possible until the SRM Client's Secure Storage Password property is set.

Configure the SRM Client's Secure Storage Password property.
OPSAPS-61278: The SRM Client’s secure storage fails to generate correctly in FIPS-enabled clusters
In a FIPS enabled cluster, the SRM Client’s secure storage fails to generate correctly. As a result, the automatically generated configuration used by the srm-control tool will contain unresolvable references, making it unusable.
There are two workarounds for this issue. Choose one of the following:
  • Configure SRM using the Streams Replication Manager’s Replication Configs Cloudera Manager property.

    Ensure that all cluster connection related properties (cluster aliases, bootstrap servers, security-related properties) are added, with the appropriate prefixes, for all clusters taking part in the replication process.

  • Manually create a custom configuration file and use it with the srm-control tool.
    1. Create a copy of the default configuration located at /etc/streams_replication_manager/conf/
    2. Update all security related properties in the copy with the appropriate values.
      The values that you must update are similar to the following example:
      Ensure that you replace all ${...} references with actual values such as the key and truststore locations, passwords, and so on.
    3. Run the srm-control tool using the --config option.
      For example:
      srm-control topics --config [***PATH TO CUSTOM CONFIGURATION FILE***] --source [***SOURCE_CLUSTER***] --target [***TARGET_CLUSTER***] --add [***TOPIC1***],[***TOPIC2***]


SRM cannot replicate Ranger authorization policies to or from Kafka clusters
Due to a limitation in the Kafka-Ranger plugin, SRM cannot replicate Ranger policies to or from clusters that are configured to use Ranger for authorization. If you are using SRM to replicate data to or from a cluster that uses Ranger, disable authorization policy synchronization in SRM. This can be achieved by clearing the Sync Topic Acls Enabled (sync.topic.acls.enabled) checkbox.