ai-yang commented on issue #10700: URL: https://github.com/apache/rocketmq/issues/10700#issuecomment-5634026941
Thanks @unbridled-41 for identifying the overlap and offering to consolidate #10992. I have linked it in #10701 and clarified the coverage: - Both PRs address the classic-manager first-map initialization race. - #10701 additionally addresses RocksDB v1 initialization, LMQ map allocation, and ordering of whole-map incremental WAL writes, with restart verification. - The existing classic regression in #10701 forces the conflicting first reads and verifies persistence through a JSON round trip, so I have kept that test for now. #10701 currently has all 10 CI checks passing. @RongtongJin @lizhimins, could you review the broader fix and advise on consolidation? If you prefer the classic-only change first, I can adjust the remaining RocksDB v1 scope after that decision. -- 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]
