GenerousMan opened a new issue, #7689: URL: https://github.com/apache/rocketmq/issues/7689
### 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 During my testing of the controller mode, I encountered a scenario that could lead to message loss: 1. The leader controller and master broker are killed simultaneously. 2. Both are restarted at the same time, with the master broker completing recovery and immediately having messages written to it. ### RocketMQ version 5.1.4 ### JDK Version _No response_ ### Describe the Bug Since the master only recovers up to the position of the confirmOffset upon recovery, there may still be some messages that have not been synchronized by the slave. As a result, the data in the cqOffsetTable might be inaccurate. At this time, newly written messages could share the CQ offset with messages after the confirmOffset—this could lead to message loss. ### Steps to Reproduce using openchaos, major-kill. Killing brokers and controllers in the same time. ### What Did You Expect to See? no message lost. ### What Did You See Instead? message lost. ### 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
