gaoyf opened a new issue, #6881:
URL: https://github.com/apache/rocketmq/issues/6881

   ### 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
   
   OS: CentOS 6.9
   
   ### RocketMQ version
   
   branch: (develop|tag 5.1.1) version: 5.1.1
   
   ### JDK Version
   
   JDK: 1.8.0_202
   
   ### Describe the Bug
   
   When I upgrade the broker from 4.9.1 to 5.1.1, when the broker starts to 
load data for more than 10 seconds, then the [persist timing 
task](https://github.com/apache/rocketmq/blob/develop/broker/src/main/java/org/apache/rocketmq/broker/schedule/ScheduleMessageService.java#L98)
 in ScheduleMessageService will be executed, but the load method has not been 
executed yet, so the existing deleyOffset.json overwrites, eventually causing 
the schedule message to be replayed.
   
   ### Steps to Reproduce
   
   As long as you find a broker with a scheduled message, and the commitlog 
reaches hundreds of G, it can be reproduced after starting with 5.x for more 
than 10 seconds. You can refer to the [case I 
wrote](https://blog.csdn.net/a417930422/article/details/131126969) for details.
   
   ### What Did You Expect to See?
   
   the messages in the delay queue are not replayed when I upgraded broker.
   
   ### What Did You See Instead?
   
   the messages in the delay queue are replayed when I upgraded broker.
   
   ### 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]

Reply via email to