We’ve been using MM2 one way for Active/Passive clusters for several years now. We started running into issues with 3.5.1. It hasn’t been keeping up with with consumer offset like it used to. To test this out we’ve done rollbacks to 3.4.0 and the offset issue corrects itself. Looking at the issue log it seems like some things around offset management have been corrected in 3.6.1 and 3.7.0. Unfortunately, we tried upgrading all the way to 3.7.0 and found the issue still remains. It doesn’t seem to matter if it’s the low-volume non-prod clusters or high-volume prod clusters. Some topics are dozen or so behind, others are hundreds of messages behind. When I look at the offsets-sync topic it seems to be producing meaningful data. And of course the messages themselves are fully insync.
Since we’re using Strimzi put the question to Jakob and he suggested changing offset.lag.max to different lower values, but that didn’t really move the needle. What changed between 3.4.0 and later versions? Are there configuration changes we should look at? ________________________________ This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, please be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender. Disclaimer R001.0
