longkaimao opened a new issue, #24543: URL: https://github.com/apache/shardingsphere/issues/24543
## Bug Report Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? ShardingSphere 4.1.1 + Seata1.6.0 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingJDBC ### Expected behavior transaction rollbacked ### Actual behavior transaction can not rollback ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. When an exception occurs, the rollback fails.It request twice, but fail once,The following is the failure log: 2023-03-10 16:39:58.637 INFO [OLE_1_5_32] i.s.r.d.u.AbstractUndoExecutor [] : compare row failed, rowKey 141911730266570754, reason [newRow is null] 2023-03-10 16:39:58.661 INFO [OLE_1_5_32] i.s.r.d.DataSourceManager [] : branchRollback failed. branchType:[AT], xid:[82.157.70.56:8091:7845639199930667123], branchId:[7845639199930667125], resourceId:[jdbc:mysql://82.157.70.56:3306/seata_order_0], applicationData:[null]. reason:[Branch session rollback failed because of dirty undo log, please delete the relevant undolog after manually calibrating the data. xid = 82.157.70.56:8091:7845639199930667123 branchId = 7845639199930667125] 2023-03-10 16:39:58.661 INFO [OLE_1_5_32] io.seata.rm.AbstractRMHandler [] : Branch Rollbacked result: PhaseTwo_RollbackFailed_Unretryable 2023-03-10 16:39:58.676 INFO [221-exec-2] s.t.a.DefaultGlobalTransaction [] : Suspending current transaction, xid = 82.157.70.56:8091:7845639199930667123 -- 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]
