Hi all
I see for mm2, mirrored topic name will have source kafka cluster put as
prefix, but consumer group doesn't, why not put consumer group naming same as
topic? is it because consumer group/offset mirroring not only from source-kafka
to remote-kafka but also from remote-kafka to source-kafka, so we need to make
sure consumer group name are same across kafkas?
I made a test and it looks like consumer group offset mirroring is one-way:
say, I have topic/acl(consumer group) created in source-kafka, and produce and
consume message from source-kafka, and I can see topic and consumer group
offset are mirrored to remote-kafka, this is very good, but when I produce to
source-kafka and consume from remote-kafka, I see consumer group offset is
updated in remote-kafka, but not updating the source-kafka, in my mm2 config I
put them cross-mirrored, so in this case, even I consume from remote-kafka, I
would expect source-kafka get consumer group offset updated, but it is not,
what do I miss? or what is the best practice with mm2? produce and consume from
source-kafka and mirror to remote? or produce to source-kafka and consume from
remote-kafka, but offset not mirrored to source!
{{ kafka01_name }}->{{ kafka02_name }}.enabled=true
{{ kafka02_name }}->{{ kafka01_name }}.enabled=true
{{ kafka01_name }}->{{ kafka02_name }}.sync.group.offsets.enabled = true
{{ kafka02_name }}->{{ kafka01_name }}.sync.group.offsets.enabled = true
topics=.*
groups=.*
