SERVER-39124 Mongos should abort cleared participants between retries of transaction statements

1 files changed, 4 insertions, 5 deletions

diff --git a/src/mongo/db/transaction_participant.cpp b/src/mongo/db/transaction_participant.cpp
index 5e7323acc45..dd1fd62b229 100644
--- a/src/mongo/db/transaction_participant.cpp
+++ b/src/mongo/db/transaction_participant.cpp
@@ -459,11 +459,10 @@ void TransactionParticipant::beginOrContinue(TxnNumber txnNumber,
                 "transaction number",
                 serverGlobalParams.clusterRole != ClusterRole::None);
 
-        // The active transaction number can only be reused if the transaction is not in a state
-        // that indicates it has been involved in a two phase commit. In normal operation this check
-        // should never fail.
-        const auto restartableStates =
-            TransactionState::kInProgress | TransactionState::kAbortedWithoutPrepare;
+        // The active transaction number can only be reused if the transaction is aborted and has
+        // not been involved in a two phase commit. Assuming routers target primaries in increasing
+        // order of term and in the absence of byzantine messages, this check should never fail.
+        const auto restartableStates = TransactionState::kAbortedWithoutPrepare;
         uassert(50911,
                 str::stream() << "Cannot start a transaction at given transaction number "
                               << txnNumber