GenerousMan opened a new issue, #7979: URL: https://github.com/apache/rocketmq/issues/7979
### 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 Ubuntu ### RocketMQ version 5.2.0 ### JDK Version _No response_ ### Describe the Bug When a timing message is deleted, it is implemented by sending a delete message. Since the timerlog of the timing message is actually an index, it cannot be verified in real time whether the deletion is valid, so -1 will be directly set to the metric when received. This will lead to a problem: if the deletion behavior is invalid, the -1 operation will not be compensated, and may even cause the metric to become a negative number - which is unacceptable. ### Steps to Reproduce according to the description of the bug. ### What Did You Expect to See? the abnormal -1 should be compensated. ### What Did You See Instead? -1 will always be there. ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
