RongtongJin opened a new issue, #7480: URL: https://github.com/apache/rocketmq/issues/7480
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Linux ### RocketMQ version 5.1.4 ### JDK Version 1.8 ### Describe the Bug The offset in the timerCheckPoint will not be corrected when the commitlog and consumeQueue are truncated  Then currentOffset is not moving  Timer messages are lost ### Steps to Reproduce https://github.com/apache/rocketmq/pull/7468 Regarding the validation of this PR, when performing an in-place upgrade on a broker with data and both enabledAppendPropCRC and forceVerifyPropCRC are set to true, the commitlog and consumeQueue are truncated. However, the currentQueueOffset in TimerMessageStore remains stuck. ### What Did You Expect to See? The currentQueueOffset in timerMessageStore will be corrected when the commitlog and consumeQueue are truncate ### What Did You See Instead? The currentQueueOffset in timerMessageStore remains stuck. ### Additional Context _No response_ -- 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: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org