GitHub user YongGoose edited a comment on the discussion: Enhancing Transaction Handling for TimeoutRollbacked and Rollbacked States
> Your compensation behavior may still fail within a certain time frame. I hadn't thought about that part, thank you :) > So I think it may be more appropriate to compensate by timing tasks and > delaying tasks. I agree with that suggestion. So, instead of creating a separate scheduled task to handle rollback and commit states for all transactions as mentioned in the comment below, would it be sufficient to process only the failed transactions in the end? > Since both of these probabilities are very low, the final result is that they > are both deleted. If you think it is necessary to handle rollbacked > transactions during runtime, I suggest that you create a separate scheduled > task to batch process transactions in the rollbacked and committed states, > rather than blocking transactions that urgently need to be rolled back and > retried. PS. Would it be possible to ask for a more detailed design? I previously wrote a post on the mailing list to propose a solution for a different issue, and I think the methods mentioned there might also be worth considering in this discussion. - https://lists.apache.org/thread/xlkshkqs5v2hflp10jgz418kos8vwrsc GitHub link: https://github.com/apache/incubator-seata/discussions/7146#discussioncomment-12108430 ---- 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
