LetLetMe commented on issue #8589: URL: https://github.com/apache/rocketmq/issues/8589#issuecomment-2367894420
> 在第二阶段时，当 RocketDB 开始写入 cq 位点，但在一些场景下，内存中的 cq(RocksDBConsumeQueueStore#bufferDRList) 数据没有完成持久化。重启时，原来文件版cq 是正常的，但 rocketdb 中的 cq 有些缺失，也就说如何保障原来 cq 和 RocketDB 中的 cq 事务性 > > In the second phase, when RocketDB starts writing the cq(RocksDBConsumeQueueStore#bufferDRList) offset, there are scenarios where the cq data in memory hasn't been fully persisted. Upon reboot, the original file-based cq is intact, but there are some losses in the cq within RocketDB. This raises the question of how to ensure the transactional consistency between the original cq and the cq in RocketDB 1. 如果双写过程中出现kvCq重启导致落后，那我们什么都不需要做，多双写一段时间，等待再次对齐就好了 2. 如果是kv模式下重启，那么会走正常的revover逻辑 -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
