zhuyuemufeng opened a new issue, #6984: URL: https://github.com/apache/rocketmq/issues/6984
### 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 window11 ### RocketMQ version 5.1.1 ### JDK Version Oracle JDK 8 ### Describe the Bug I am a little confused about the logic of the org.apache.rocketmq.store.timer.TimerMessageStore.TimerEnqueuePutService class. A single message write failure or timeout causes the entire collection to be rewritten. This causes the batch of timing messages to repeat. Why not judge the state in the loop, and only repeatedly post the message that failed to write?  If I change it like this，what problems will occur  ### Steps to Reproduce debug model ### What Did You Expect to See? only repeatedly post the failed message ### What Did You See Instead? batch repeat ### 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]
