Defining co-located Kafka clusters using a service dependency

Before you can start replicating data with Streams Replication Manager (SRM), you must define the co-located Kafka clusters that take part in the replication process. This can be done by enabling a service dependency between the SRM service and the co-located Kafka cluster, specifying an alias for the co-located cluster, and configuring security related properties.

The following list of steps walk you through how you can define the co-located Kafka cluster using a service dependency.

Ensure that you have reviewed Defining and adding clusters for replication and understand that the following list of steps are only one part of the full configuration workflow.

  1. In Cloudera Manager, go to Clusters and select the Streams Replication Manager service.
  2. Go to Configuration.
  3. Configure the co-located cluster:
    1. Find and enable the Kafka Service property.
    2. Find and configure the Streams Replication Manager Co-located Kafka Cluster Alias property.
      The alias you configure represents the co-located cluster. Enter an alias that is unique and easily identifiable. For example:
    3. Optional: If the co-located cluster uses any type of security, enable the relevant security feature toggles.
      • If the cluster uses TLS/SSL, enable the following properties:
        • Enable TLS/SSL for SRM Driver
        • Enable TLS/SSL for SRM Service
      • If the cluster uses Kerberos authentication, enable the Enable Kerberos Authentication property.
      • If the cluster uses TLS/SSL and Kerberos, enable all three properties.
The co-located Kafka cluster is defined using a service dependency.
Add both external and co-located Kafka clusters to SRM’s configuration.