ShadowySpirits commented on issue #5174: URL: https://github.com/apache/rocketmq/issues/5174#issuecomment-1260565111
> If client can specify timestamp, that's ok. But all the timestamps used in consumeMessageDirectly are calculated inner, client cannot control unless implements a special MqAdminExt. Sorry, I don't get your point. The consumeMessageDirectly will call viewMessage method and decode broker IP and message phyOffset. And then, use this IP and offset to fetch message from broker. I find nothing about the born timestamp in this process. > From the code, this problem could reproduce as long as the storeTimestamp less than bornTimestamp, even if storeTimestamp were just 1ms behind. There is a simple way to alleviate this problem. Each born timestamp using in mqadmin minus a fixed time by default, such as 3s. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
