You could check whether the producers on the source cluster are using some
compression algo. Use the same one on mm2 as currently it will decompress
and then write again to the target cluster uncompressed unless you
configure it.
On Sun, Feb 6, 2022 at 05:20 Kafka Life wrote:
> Dear Kafka Expert
Dear Kafka Experts , Need your advice please
I am running a mirror maker in kafka 2.8 to replicate a topic from kafka
0.11 instance.
The size of each partition for a topic on 0.11 is always in 5 to 6 GB but
the replicated topic in 2.8 instances is in 40 GB for the same partition.
The topic config
