[SERVER-70247] SyncTransactionWithRetries used with SEPTransactionClient can leave transactions open when runNoThrow opCtx gets cancelled - MongoDB Jira

XML

Word

Printable

JSON

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Sprint:
Sharding 2022-10-17, Sharding NYC 2022-10-31, Sharding NYC 2022-11-14

Sequence of events:

SyncTransactionWithRetries::runNoThrow gets called
Waits for the transaction callback to finish here, but opCtx was cancelled so proceed to call cancel on the cancellation token
If the transaction hasn't finished, it will try to abort it. But since it is using the client's runCommand to run abort, it will fail because it will try to use the token that was already cancelled to create the new opCtx for the abort command
Transaction that was started at the beginning is just left in idle state.

is related to

SERVER-71649 Transaction API shouldn't block on an uncancelable operation

related to

SERVER-70248 Race in ShouldBeSafeToRetryOnStepDown test can lead to hang