GitHub user funky-eyes added a comment to the discussion: Enhancing Transaction Handling for TimeoutRollbacked and Rollbacked States
I understand that your design is to quickly trigger compensation for failed events by adding monitoring events for transaction end status results. But one thing needs to be made clear. The failure of transactions in the end status is most likely due to network and disk problems. Your compensation behavior may still fail within a certain time frame. And in your design, the process looks like a memory queue? In Seata's storage mode, only file and raft transaction data are in memory, while db and redis are external storage. So I think it may be more appropriate to compensate by timing tasks and delaying tasks. GitHub link: https://github.com/apache/incubator-seata/discussions/7146#discussioncomment-12107873 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
