contrueCT commented on issue #9791: URL: https://github.com/apache/rocketmq/issues/9791#issuecomment-3489895238
Your solution approach is excellent! My idea is that users can actually customize an appropriate state-checking logic when implementing the transaction status check method `TransactionListener.checkLocalTransaction(MessageExt msg)` (for example, using a distributed state cache, like managing shared transaction states within the group via Redis), ensuring that producers in the same producer group return the same check results. This aligns with RocketMQ's design principle of consistent behavior within the same producer group, while potentially causing a slight decrease in concurrent performance, thus preserving design flexibility. -- 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]
