Andrew, The broker appears to be rejecting the timestamp of the replicated record, which is the same as the source record timestamp in MM2. I think you will need to relax the timestamp validation, which is controlled by these configurations:
https://kafka.apache.org/documentation/#topicconfigs_message.timestamp.difference.max.ms https://kafka.apache.org/documentation/#brokerconfigs_log.message.timestamp.difference.max.ms I believe that if you want 5-day old timestamps to be preserved, that this configuration must be at least 5 days either globally or just for your destination topic. I hope this helps! Greg Harris On Tue, May 2, 2023 at 12:49 PM An, Hongguo (CORP) <hongguo...@adp.com.invalid> wrote: > Hi: > When I am running MM2 (3.4.0), any message older than 1 days are not > copying, the topic has retention period as 5 days. > Got error: > > org.apache.kafka.common.errors.InvalidTimestampException: Timestamp > 1682664968019 of message with offset 0 is out of range. The timestamp > should be within [1682965965321, 1683138765321] > > Please help > > Thanks > Andrew > > > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. > If the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, notify the sender immediately by > return email and delete the message and any attachments from your system. >
