Re: Mirror maker rejecting messages due to low message.timestamp.difference.max.ms

I think I was on the right lines here but I suspect the cycle detection in
shouldReplicateTopic prevents source topics updating target topics with the
same name - so once the topic configuration has been synced once, it will
not be synced again.

The combination of use.defaults.from = source and config.properties.exclude
seems to have done the trick (in the end I set both use.defaults.from and
source->target.use.defaults.from - I'm not sure whether that was necessary
but also I didn't want to burn further hours on cluster rebuilds to work it
out) and message.timestamp.difference.max.ms is now Long.MAX

After a target cluster build the message replication appears to be
proceeding without the timestamp validation rejections.

--


Disclaimer: This e-mail and any attachments may contain Confidential
Information. If you are not the intended recipient, any disclosure,
copying, distribution or use of any information contained herein is
strictly prohibited. If you have received this transmission in error,
please immediately notify the Security Officer, and destroy the original
transmission and any attachments without reading or saving.