For more detailed information, you can add links to related documents to review.
Warm regards, Ji Min justabug <[email protected]> 于2024年1月26日周五 14:55写道： > I am writing to provide you with the minutes from our community meeting > held on January 24, 2024. > The meeting was productive, and we covered > several topics and conclusion as outlined below: > > Moderator: Minghua Xie > > *Attendees* Minghua Xie,Min Ji,Chen Jianbin,Cheng > Xingyuan,Wang Liang,Mu Sheng,Tang Rulin totaling 7 people. > > > *Discussion items:* > > 1. Is `branchtype` TCC or a new type? > - It is TCC, as RocketMQ still joins the global transaction > in TCC mode. > > > 2. Should it proxy `send()` or `sendMessageInTransaction()`? > - Only proxy `send`, not half messages. > - Only proxy `send(msg)` and `send(msg, timeout)`, other > methods are not supported officially. > > > 3. Provide a separate producer or create a dynamic proxy for an existing > producer? > - Provide an independent producer, along with a separate > listener. > > > 4. If the first phase is not completed, the broker will perform a > re-check. How to know the status of the global transaction during this > re-check? > - The message header contains the xid. Use the globalStatus > interface to check the status of xid for the phase2 （commit/rollback） of > the half message. > > > 5. How to resolve the issue of incomplete information for broker re-check > due to accidental interruption in the first phase leading to the second > phase? > - If the xid does not exist during the re-check, it means the > transaction has been rolled back completely, so proceed with the rollback. > - If there is no half message's msgid during the rollback, it > directly indicates that the branch has already been rolled back, as the > message will be automatically rolled back according to the fifth point. > > > 6. How to handle scenarios with multiple producers corresponding to > multiple RocketMQ clusters? > - Currently, this is not supported.
