Frequently Asked Questions (FAQs)

Looking for Confluent Cloud Cluster Linking docs? You are currently viewing Confluent Platform documentation. If you are looking for Confluent Cloud docs, check out Cluster Linking on Confluent Cloud.

FAQ Quick List

Q&As

Frequently Asked Questions

How do I know the data was successfully copied to the destination and can be safely deleted from the source topic?

Each mirror topic has a metric called “Max Lag” which is the maximum number of messages any of its partitions are lagging by. You can monitor this through the Metrics API, Confluent Cloud Console, or Confluent Control Center.

If you need partition-level guarantees, you can use the REST API or the CLI to describe a mirror topic and see the exact offset that each partition has replicated up to. It will be called “Last Source Fetch Offset.” Anything before that offset in that partition has been replicated.

How is the consumer offset sync accomplished?

Consumer offset sync does not mirror the internal topic _consumer_offsets, but rather uses code for the controller nodes to sync the offsets on a frequency that you can configure. To learn more, see “Syncing consumer group offsets” in mirror topics on Confluent Cloud and mirror topics on Confluent Platform.

Can I modify consumer group filters on-the-fly?

Yes, you can modify the consumer group exclude or include filters without having to stop and restart the cluster link. However, if you add consumer groups to the exclude list that were already synced, then you will need to manually delete them on the mirrored destination if you want them removed immediately. Cluster Linking does not delete consumer groups. In Confluent Cloud, consumer offsets are retained for 7 days (and automatically deleted after 7 days). To learn more, see “Syncing consumer group offsets” in mirror topics on Confluent Cloud and mirror topics on Confluent Platform.

How do I create a mirror topic?

You can create a specific mirror topic using the Confluent Cloud Console, the Confluent Cloud REST API, the Confluent CLI, the Confluent Platform AdminClient API, or Confluent for Kubernetes. Alternatively, you can configure your cluster link to automatically create mirror topics that match certain prefixes. To learn more, see Mirror Topic Creation.

Can I use Cluster Linking without the traffic going over the public internet?

Some customers want to use a public Confluent Cloud cluster, but do not want the Cluster Linking traffic in/out of it to traverse the public internet.

Today, there is no way to give a Confluent Cloud cluster both a public and a private bootstrap server. Therefore, any traffic that goes to the public Confluent Cloud cluster will use its public bootstrap server, regardless of which method is used (Cluster Linking, Replicator, consumer/producers, and so on).

On Amazon AWS and Microsoft Azure, traffic between two endpoints that are both on the same cloud service provider (CSP) (for example, AWS in us-west-2 to AWS in us-east-1, or Azure UK South to Azure UK West) always stays on that CSP’s backbone. So, if the two clusters you are using with Cluster Linking are on the same cloud, the traffic will stay on that CSP’s backbone and will not cross over to the public internet. See the guarantees provided in the Amazon AWS documentation and the Microsoft Azure documentation.

Does Schema Linking have the same limitations as Cluster Linking for private networking and cross-region?

No, Schema Linking does not have the same limitations as Cluster Linking for private networking. Schema Linking is always deployed on the public internet, and therefore is available between any two Confluent Cloud schema registries, regardless of the Kafka clusters’ network. For example, a distributed, VPC peered deployment can always use Schema Linking, regardless of cross-region factors, because the Schema Registry clusters communicate over public internet, unlike their associated Kafka clusters.

I need RPO==0 (guarantee of no data loss after a failover) in Confluent Cloud. What can I do?

Cluster Linking has “asynchronous replication”, meaning it does not have an RPO==0 (also known as “synchronous”) option out-of-the-box. Achieving RPO==0 with asynchronous replication is architecturally complex. It requires producers to have a durable, multi-region cache of their most recent data. After a failover, the producers need to replay the data from the cache. This will result in duplicate events in the underlying topics, which your consumers need to tolerate.

If I want to join two topics from different clusters in ksqlDB, how can Cluster Linking help me?

A ksqlDB application can only interact with one Apache Kafka® cluster. Cluster Linking can be used to bring a topic from another cluster into a local copy on your cluster. Then, you can use ksqlDB to join the local copy (the “mirror topic”) with the second topic.

Does Cluster Linking work with mTLS?

For Confluent Platform, yes, you can use mTLS. (See Mutual TLS (mTLS) in the Cluster Linking on Confluent Platform documentation.)

On Confluent Cloud, it depends:

  • For Confluent Cloud to Confluent Cloud clusters: no, TLS and SASL are used under the hood.
  • For data coming into Confluent Cloud from open-source Apache Kafka®: yes, you can use mTLS.
  • For data coming into Confluent Cloud from Confluent Platform: you can use either mTLS or source-initiated cluster links with TLS+SASL. You cannot use mTLS with source-initiated cluster links.

How does Schema Registry multi-region disaster recovery (DR) work in Confluent Cloud?

Confluent Cloud Schema Registry is a three node cluster spanning three different zones within a region (multi-zone), meaning it can tolerate two node failures in that region. For multi-region DR, you can use Schema Linking to replicate and keep in sync schemas across two Schema Registry clusters in different regions.

How can I automatically failover Kafka clients?

On Confluent Cloud: A detailed solution for how to failover clients as quickly as possible will be published as a whitepaper. Please check back on these FAQs in a few weeks.

On Confluent Platform, customers have more control than those on Confluent Cloud. This gives you an additional option:

  • Use a Domain Name System (DNS) service (such as Amazon Route 53) to direct Kafka clients to the “active” cluster. In this scenario, the bootstrap server points to a URL, and you update the DNS to have that URL resolve to the “active” cluster. Kafka clients do not need to change their bootstrap server on a failover.
  • Use the same authentication information on both clusters; so Kafka clients do not need to change their security configuration on a failover.

So, to failover clients, you simply change the DNS. When the clients start up, they will bootstrap to the “active” cluster.

The only thing to keep in mind here is that bootstrapping only happens when a client starts up. (This is an advantage of Multi-Region Clusters, since it avoids the re-bootstrapping process.) If you have any clients that are still running and survived the outage, they will need to have a way to restart in order to failover. This is less of a concern in Confluent Cloud, for two reasons:

  • Often a restart can be called by the Operator, if all clients are running on K8’s (Kubernetes) clusters.
  • On Confluent Cloud, the outage is a cloud service provider (CSP) outage in a given region. Let’s say your clients are all in the same region as the cluster they point to. For example, for an Amazon AWS cluster, suppose all clients are also on AWS and in the same region as the cluster. If there is an AWS outage in that region, no clients will survive the outage; they will all need to be restarted anyways, by definition.

How does Cluster Linking optimize network bandwidth and performance in Confluent Cloud?

Cluster Linking is a direct connection between two clusters, and retains the compression set on any topics and messages that it mirrors. This is an improvement over both Confluent Replicator and MirrorMaker 2, which require a second network hop to write the data, and do not retain compression.

For customers using Cluster Linking on Confluent Cloud, which is a fully managed service, you only need to care about:

  • Total bytes sent, as this is what Confluent bills on.
  • Throughput that can be achieved. Cluster Linking uses the throughput allocated to the clusters (50MB/s in and 150MB/s out per CKU) and is capable of maxing out that throughput as needed, even in high latency scenarios like between cloud providers or regions that are far apart from each other.

Does Cluster Linking support compacted topics?

Yes, Cluster Linking works with compacted topics; which are mirrored as such from source to destination.

Compacted topics are configured to retain only the newest record for each key on a topic, regardless of retention period expiration on the message. This reduces the storage requirements for a topic and supports log compaction. This can be configured when you create a topic; for example, kafka-topics --topic topic_name --bootstrap-server localhost:9092 --config "cleanup.policy=compact" --create. The log can be configured as log.cleanup.policy=compact in $CONFLUENT_HOME/etc/kafka/server.properties.