-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Sharding NYC 2022-05-30, Sharding NYC 2022-06-13
Currently, the TransactionParticipant does not abort internal transactions for the previous txnNumber (i.e. retryable internal transactions) when starting a new txnNumber like it does for regular transactions. Those dangling in-progress transactions should not lead to any hang but they hold on to some resources so we may want to abort them.