Hi, We are using MirrorMaker to backup topics. We noticed that repartition topics created by Kafka Streams applications seem to keep increasing in size in the target cluster compared to the source cluster. This makes sense according to the documentation of org.apache.kafka.streams.kstream.KStream#repartition():
"Similar to auto-repartitioning, the topic will be created with infinite retention time and data will be automatically purged by Kafka Streams." In other words, since we do not have the Kafka Streams applications running in the target cluster, the automatic purge is not happening. Are we understanding this correctly? How do we ensure that we back up the source cluster without losing data and without the target cluster size increasing beyond the source cluster size? Is MirrorMaker even the right choice of tool? Do we need to consider Replicator or Cluster Linking? I originally asked this question on Stack Overflow without any luck: https://stackoverflow.com/questions/66599230/mirrored-repartition-topics-keep-increasing-in-size Best regards, Martin Internal
