SERVER-35707 Allow mongos to retry on re-targeting errors in a transaction

1 files changed, 3 insertions, 1 deletions

diff --git a/jstests/core/txns/concurrent_drops_and_creates.js b/jstests/core/txns/concurrent_drops_and_creates.js
index 5ddf7ca260b..8db02f1ae98 100644
--- a/jstests/core/txns/concurrent_drops_and_creates.js
+++ b/jstests/core/txns/concurrent_drops_and_creates.js
@@ -64,7 +64,9 @@
     // since the transaction's read timestamp. Since our implementation of the in-memory collection
     // catalog always has the most recent collection metadata, we do not allow you to read from a
     // collection at a time prior to its most recent catalog changes.
-    assert.commandFailedWithCode(sessionCollB.insert({}), ErrorCodes.SnapshotUnavailable);
+    const isMongos = assert.commandWorked(db.runCommand("ismaster")).msg === "isdbgrid";
+    const expectedCode = isMongos ? ErrorCodes.NoSuchTransaction : ErrorCodes.SnapshotUnavailable;
+    assert.commandFailedWithCode(sessionCollB.insert({}), expectedCode);
     assert.commandFailedWithCode(session.abortTransaction_forTesting(),
                                  ErrorCodes.NoSuchTransaction);