LetLetMe opened a new issue, #8699: URL: https://github.com/apache/rocketmq/issues/8699
### 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 all ### RocketMQ version all ### JDK Version all ### Describe the Bug 在cq双写方案中，当双写切换到只读rocksdbcq时，发现了问题要回滚，offset和topic等可以通过json格式导出，下次broker启动时会自动marge加载（当然offset可能是时刻滚动的，这个过程中还是会出现少量的消息重复）。 同时，文件版cq的补偿构建也是需要做的。 In the CQ dual-write scheme, when switching to read-only RocksDB CQ and an issue is discovered requiring a rollback, the offset and topic can be exported in JSON format. Upon the next broker startup, they will automatically merge and load (though offsets might be constantly rolling, leading to a small number of message duplications during this process). Additionally, compensation construction for the file-based CQ is also necessary. ### Steps to Reproduce 当回滚时补偿构建缺失的文件版cq Compensate for the missing file-based CQ during rollback. ### What Did You Expect to See? nothing ### What Did You See Instead? nothing ### Additional Context nothing -- 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]
