[KAFKA-10719] MirrorMaker2 fails to update its runtime configuration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.0
• Fix Version/s: 3.7.0, 3.6.2
• Component/s: mirrormaker
• Assignee: Unassigned
• Reporter: Peter Sinoros-Szabo
• Created: 13/Nov/20 17:17
• Updated: 14/Feb/24 19:42
• Resolved: 14/Feb/24 19:42

Description

I was running successfully the MM2 cluster with the following configuration, I simplified it a little:

 clusters = main, backup main.bootstrap.servers = kafkaA:9202,kafkaB:9092,kafkaB:9092 backup.bootstrap.servers = backupA:9092,backupB:9092,backupC:9092 main->backup.enabled = true main->backup.topics = .*

I wanted to change the bootstrap.address list of the destination cluster to a different list that is pointing to the same cluster, just a different listener with a different routing. So I changed it to:

 backup.bootstrap.servers = backupSecA:1234,backupSecB:1234,backupSecC:1234

I did a rolling restart on the MM2 nodes and say that some tasks were still using the old bootstrap addresses, some of them were using the new one. I don't have the logs, so unfortunately I don't know which one picked up the good values and which didn't. I even stopped the cluster completely, but it didn't help. Ryanne adviced to delete the mm2-config and mm2-status topics, so I did delete those on the destination cluster, that solved this issue.

Issue Links

• is fixed by: KAFKA-15372 MM2 rolling restart can drop configuration changes silently