[Bug] The offset in the timerCheckPoint will not be corrected when the commitlog and consumeQueue are truncated

[RongtongJin]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• 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

#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

[RongtongJin]

@guyinyou

[github-actions]

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

[github-actions]

This issue was closed because it has been inactive for 3 days since being marked as stale.