GenerousMan opened a new issue, #7381: URL: https://github.com/apache/rocketmq/issues/7381
### 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 macos ### RocketMQ version 5.1.3 ### JDK Version _No response_ ### Describe the Bug After the timer message is enqueueed, if the entry time wheel is slow, it will be directly thrown into the dequePutQueue, and the increment operation of metrics will not be performed. This will cause the metrics of timerMessage to be inaccurate and may even be negative. ### Steps to Reproduce just start a local broker, and send timerMessage into it. you need to set the deliver time now + 3~5ms. ### What Did You Expect to See? metrics should be the num of timer messages in the timing wheel. ### What Did You See Instead?  ### 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
